Method and system for automatically detecting media and implementing interaction control thereon

ABSTRACT

A method for automatically detecting media and implementing interaction control thereon. The present method receives a media change notification (MCN) from a non-defeatable autorun. After receiving the MCN of a media event an operation is automatically executed. The operation then initiates a controller for controlling interaction of deliverable electronic media from a media file corresponding to the media event, wherein the receiving, executing, and controlling are automatically implemented and cannot be defeated by a user.

FIELD OF THE INVENTION

The present invention relates to media change on a computing system.More particularly, the present invention relates to a method forautomatically detecting media and implementing interaction controlthereon.

BACKGROUND OF THE INVENTION

With advancements in hardware and software technology, computers areintegral tools utilized in various applications, such as finance, CAD(computer aided design), manufacturing, health care, telecommunication,education, etc. Further, an enhancement in computer functionality can berealized by communicatively coupling computers together to form anetwork. Within a network environment, computer systems enable users toexchange files, share information stored in common databases, combine,or pool resources, communicate via electronic mail (e-mail), and accessinformation on the Internet. Additionally, computers connected to anetwork environment, e.g., the Internet, provide their users access todata and information from all over the world.

Some of the various types of data that a user can access and shareinclude, but are not limited to, text data such as that found in a worddocument, graphical data such as that found in pictures, e.g., JPEGs,GIFs, TIFFs, audio data such as that found in music files, e.g., MP3files, and video data such as that found in moving pictures files, e.g.,MPEG, MOV, and AVI files, to name a few. In fact, nearly any type ofdata can be stored and shared with other computer systems. In manyinstances, the material contained within the various data types iscopyrighted material.

There are many different types of network environments that can beimplemented to facilitate sharing of data between computer systems. Someof the various network environment types include Ethernet,client-server, and wired and/or wireless network environments. A commonutilization of a network environment type is for file sharing, such asin a P2P network or point-to-point network. Most P2P networks rely onbusiness models based upon the transfer and redistribution ofcopyrighted material, e.g., audio files, between computers coupled to anetwork, e.g., the Internet. A P2P network allows a user to acquire thecopyrighted material from a computer, a web site source, or a musicbroadcaster, and store and share the material with other usersthroughout the network, in some instances acting as a web site source ora music broadcaster.

It is also common for users sharing media files in an uncontrolledmanner to use freely distributed or commercially available media playerapplications to experience, e.g., listen, view, and/or watch, the sharedfiles. In many instances, these media player applications also providefor downloading the media file from a P2P network or from licensed webbroadcasters, saving it locally, and then upload the media file onto anunlawful P2P or similar network and/or consumer recording devices.Unlawfully saving/recording a media file can be as simple as selectingthe save or record function on a media player application.

Additionally, many of the computers, web sites, and web broadcastersthat share copyrighted material commonly do not control or monitor thefiles being exchanged between computers. Additionally, when web sitesattempt to control or restrict the distribution of copyrighted material,e.g., audio files, users seeking to circumvent controls or restrictionscan, in many cases, simply utilize the recording functionality of amedia player application and save the copyrighted material, rename theparticular audio file, and upload the renamed file, rendering attemptsto control or restrict its distribution moot.

Further, many of the media player/recorder applications are designed tocapture and record incoming media files in a manner that circumventscontrols implemented by a media player application inherent to anoperating system, e.g., QuickTime for Apple, MediaPlayer for Windows™,etc., or one downloadable from the Internet, e.g., RealPlayer,LiquidAudio, or those provided by webcasters, e.g., PressPlay, forcontrolling unauthorized recording of media files. Additionally, manydigital recording devices, e.g., mini-disc recorders, MP3 recorders, andthe like, can be coupled to a digital output of a computer system tocapture the media file.

It is desired to prevent persons from making unauthorized copies ofcopyrighted material through some available network, e.g., wireline,wireless, P2P, etc., or through a communicative coupling. It is furtherdesirable to prevent persons from making unauthorized copies of mediafiles from or to alternative sources, e.g., CD players, DVD players,removable hard drives, personal electronic and/or recording devices,e.g., MP3 recorders, and the like.

Current methods of sharing media files do not provide adequateprotection against unauthorized recording of the media files.

SUMMARY OF THE INVENTION

Accordingly, a need exists for a method for automatically detectingmedia and implementing interaction control thereon. Further, a needexists for a method for automatically detecting media and implementinginteraction control thereon that cannot be turned off, blocked, ordisabled by a user. Yet another need exists for a method forautomatically detecting media and implementing interaction controlthereon which is compatible with industry standards. Embodiments of thepresent invention satisfy the above-mentioned needs.

In one embodiment, the present invention provides a method forautomatically detecting media and implementing interaction controlthereon. The present method receives a media change notification (MCN)from a non-defeatable autorun. After receiving the MCN of a media eventan operation is automatically executed. The operation then initiates acontroller for controlling interaction of deliverable electronic mediafrom a media file corresponding to the media event, wherein thereceiving, executing, and controlling are automatically implemented andcannot be defeated by a user.

In another embodiment, the present invention provides computerimplementable instructions stored on a computer readable medium, theinstructions for causing a client system to perform a method forautomatically detecting media and implementing interaction controlthereon. The present method receives a media change notification (MCN)from a non-defeatable autorun. After receiving the MCN of a media eventan operation is automatically executed. The operation then initiates acontroller for controlling interaction of deliverable electronic mediafrom a media file corresponding to the media event, wherein thereceiving, executing, and controlling are automatically implemented andcannot be defeated by a user.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and form a part ofthis specification, illustrate embodiments of the invention and,together with the description, serve to explain the principles of theinvention.

FIG. 1 is a block diagram of an exemplary computer system that can beutilized in accordance with an embodiment of the present invention.

FIG. 2 is a block diagram of an exemplary network environment that canbe utilized in accordance with an embodiment of the present invention.

FIG. 3 is a block diagram of a copyright compliance mechanism inaccordance with an embodiment of the present invention.

FIG. 4 is an exemplary system for implementing a copyright compliancemechanism in accordance with an embodiment of the present invention.

FIG. 5A is a data flow block diagram showing an implementation of acopyright compliance mechanism for preventing unauthorized recording ofmedia files, in accordance with one embodiment of the present invention.

FIG. 5B is a data flow block diagram showing an implementation of acomponent of a copyright compliance mechanism for preventingunauthorized recording of media files, in accordance with anotherembodiment of the present invention.

FIG. 5C is a data flow block diagram showing an implementation of acopyright compliance mechanism for preventing unauthorized output ofmedia files, in accordance with one embodiment of the present invention.

FIG. 5D is a data flow block diagram showing an implementation of acopyright compliance mechanism for preventing unauthorized output ofmedia files through media file capture at a kernel level, in accordancewith one embodiment of the present invention.

FIG. 6 is a block diagram of an environment for preventing unauthorizedcopying of a media file, in accordance with one embodiment of thepresent invention.

FIGS. 7A, 7B, and 7C are a flowchart of steps performed in accordancewith an embodiment of the present invention for providing a copyrightcompliance mechanism to a network of client and server computer systems.

FIG. 8 is a diagram of an exemplary global media delivery system inwhich a copyright compliance mechanism can be implemented in accordancewith an embodiment of the present invention.

FIG. 9 is a block diagram of a copyright compliance mechanisminstallable from a media storage device, in accordance with oneembodiment of the present invention.

FIG. 10 is a block diagram of a communicative environment forcontrolling unauthorized reproduction of protected media files disposedon a media storage device, in accordance with one embodiment of thepresent invention.

FIG. 11 is a data flow block diagram showing an implementation of acopyright compliance mechanism for preventing unauthorized reproductionof a protected media file located on a media storage device, inaccordance with one embodiment of the present invention.

FIG. 12 is a block diagram of components of a usage compliance mechanisminstallable from a media storage device upon which protected media filesare disposed, in accordance with one embodiment of the presentinvention.

FIG. 13 is a block diagram of components of a usage compliance mechanismand content disposed on a media storage device, in accordance with oneembodiment of the present invention.

FIG. 14 is a block diagram of a communicative environment forcontrolling presentation of content on a media storage device, inaccordance with one embodiment of the present invention.

FIG. 15 is a data flow block diagram showing an implementation of ausage compliance mechanism for controlling presentation of contentdisposed on a media storage device, in accordance with one embodiment ofthe present invention.

FIG. 16 is a flowchart of a process for controlling presentation ofcontent disposed on a media storage device, in accordance with oneembodiment of the present invention.

FIG. 17 is a block diagram of a network environment for sharing mediacontent among nodes within a network in accordance with one embodimentof the present invention.

FIG. 18 is a block diagram of components within an exemplary usagecompliance mechanism configured for utilization in a distributed networktopology for controlling media sharing among nodes in a network, inaccordance with one embodiment of the present invention.

FIG. 19 is an illustrated data flow of an exemplary system forcontrolling media sharing among multiple nodes communicatively coupledin a network in accordance with one embodiment of the present invention.

FIG. 20 is a block diagram of an exemplary computing system inaccordance with an embodiment of the present invention for providing amedia change notification.

FIG. 21 is a data flow block diagram of an exemplary method forproviding a media change notification on a computing system inaccordance with an embodiment of the present invention.

FIG. 22 is a flowchart of a method for providing a media changenotification on a computing system, in accordance with one embodiment ofthe present invention.

FIG. 23 is a flowchart of a method for automatically executing anoperation after a media event in accordance with one embodiment of thepresent invention.

FIG. 24 is a data flow block diagram for automatically detecting mediaand implementing interaction control thereon, in accordance with oneembodiment of the present invention.

FIG. 25 is a flowchart of a method for automatically detecting media andimplementing interaction control thereon in accordance with oneembodiment of the present invention.

DETAILED DESCRIPTION

Reference will now be made in detail to embodiments of the invention,examples of which are illustrated in the accompanying drawings. Whilethe invention will be described in conjunction with embodiments, it willbe understood that they are not intended to limit the invention to theseembodiments. On the contrary, the invention is intended to coveralternatives, modifications, and equivalents, which may be includedwithin the spirit and scope of the invention as defined by the appendedclaims. Furthermore, in the following detailed description of thepresent invention, numerous specific details are set forth in order toprovide a thorough understanding of the present invention. However, toone of ordinary skill in the art, the present invention may be practicedwithout these specific details. In other instances, well-known methods,procedures, components, and circuits have not been described in detailas not to unnecessarily obscure aspects of the present invention.

Some portions of the detailed description which follows are presented interms of procedures, logic blocks, processing, and other symbolicrepresentations of operations on data bits within a computing system ordigital memory system. These descriptions and representations are themeans used by those skilled in the data processing art to mosteffectively convey the substance of their work to others skilled in theart. A procedure, logic block, process, etc., is herein, and generally,conceived to be a self-consistent sequence of steps or instructionsleading to a desired result. The steps are those involving physicalmanipulations of physical quantities. Usually, though not necessarily,these physical manipulations take the form of electrical or magneticsignals capable of being stored, transferred, combined, compared, andotherwise manipulated in a computing system or similar electroniccomputing device. For reasons of convenience, and with reference tocommon usage, these signals are referred to as bits, values, elements,symbols, characters, terms, numbers, or the like, with reference to thepresent invention.

It should be borne in mind, however, that all of these terms are to beinterpreted as referencing physical manipulations and quantities and aremerely convenient labels and are to be interpreted further in view ofterms commonly used in the art. Unless specifically stated otherwise asapparent from the following discussions, it is understood thatdiscussions of the present invention refer to actions and processes of acomputing system, or similar electronic computing device thatmanipulates and transforms data. The data is represented as physical(electronic) quantities within the computing system's registers andmemories and is transformed into other data similarly represented asphysical quantities within the computing system's memories or registers,or other such information storage, transmission, or display devices.

In the following description, for purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the present invention. To one skilled in the art, thepresent invention may be practiced without these specific details. Inother instances, well-known structures and devices are shown in blockdiagram form in order to avoid obscuring the present invention.

Embodiments of the present invention are discussed primarily in thecontext of a network of computer systems such as a network of desktop,workstation, laptop, handheld, and/or other portable electronic device.For purposes of the present application, the term “portable electronicdevice” is not intended to be limited solely to conventional handheld orportable computers. Instead, the term “portable electronic device” isalso intended to include many mobile electronic devices. Such mobiledevices include, but are not limited to, portable CD players, MP3players, mobile phones, portable recording devices, satellite radios,portable video playback devices (digital projectors), personal videoeyewear, and other personal digital devices. Additionally, embodimentsof the present invention are also well suited for implementation withtheater presentation systems for public and/or private presentation intheaters, auditoriums, convention centers, etc.

FIG. 1 is a block diagram illustrating an exemplary computer system 100that can be used in accordance with embodiments of the presentinvention. It is noted that computer system 100 can be nearly any typeof computing system or electronic computing device including, but notlimited to, a server computer, a desktop computer, a laptop computer, orother portable electronic device. Within the context of embodiments ofthe present invention, certain discussed processes, procedures, andoperations can be realized as a series of instructions (e.g., a softwareprogram) that reside within computer system memory units of computersystem 100 and are executed by a processor(s) of computer system 100.When executed, the instructions cause computer system 100 to performspecific actions and exhibit specific behavior which is described indetail herein.

Computer system 100 of FIG. 1 comprises an address/data bus 110 forcommunicating information, one or more central processors 101 coupled tobus 110 for processing information and instructions. Centralprocessor(s) 101 can be a microprocessor or any alternative type ofprocessor. Computer system 100 also includes a computer usable volatilememory 102, e.g., random access memory (RAM), static RAM (SRAM), dynamicRAM (DRAM), synchronous dynamic RAM (SDRAM), double data rate RAM (DDRRAM), etc., coupled to bus 110 for storing information and instructionsfor processor(s) 101. Computer system 100 further includes a computerusable non-volatile memory 103, e.g., read only memory (ROM),programmable ROM (PROM), electronically programmable ROM (EPROM),electrically erasable PROM (EEPROM), flash memory (a type of EEPROM),etc., coupled to bus 110 for storing static information and instructionsfor processor(s) 101. In one embodiment, non-volatile memory 103 can beremovable.

System 100 also includes one or more signal generating and receivingdevices (e.g., signal input/output device(s) 104) coupled to bus 110 forenabling computer 100 to interface with other electronic devices.Communication interface 104 can include wired and/or wirelesscommunication functionality. For example, in one embodiment,communication interface 104 is a serial communication port, but canalternatively be one of a number of well known communication standardsand protocols, e.g., a parallel port, an Ethernet adapter, a FireWire(IEEE 1394) interface, a Universal Serial Bus (USB), a small computersystem interface (SCSI), an infrared (IR) communication port, aBluetooth wireless communication adapter, a broadband connection, asatellite link, an Internet feed, a cable modem, and the like. Inanother embodiment, a digital subscriber line (DSL) can be implementedas signal input/output device 104. In such an instance, communicationinterface 104 may include a DSL modem.

Computer 100 of FIG. 1 can also include one or more computer usable datastorage device(s) 108 coupled to bus 110 for storing instructions andinformation, in one embodiment of the present invention. In oneembodiment, data storage device 108 can be a magnetic storage device,e.g., a hard disk drive, a floppy disk drive, a zip drive, or othermagnetic storage device. In another embodiment, data storage device 108can be an optical storage device, e.g., a CD (compact disc), a DVD(digital versatile disc), or other alternative optical storage device.Alternatively, any combination of magnetic, optical, and alternativestorage devices can be implemented, e.g., a RAID (random array ofindependent disks or random array of inexpensive discs) configuration.It is noted that data storage device 108 can be located internal and/orexternal of system 100 and communicatively coupled with system 100utilizing wired and/or wireless communication technology, therebyproviding expanded storage and functionality to system 100. It isfurther noted that nearly any portable electronic device, e.g., device100 a, can also be communicatively coupled with system 100 viautilization of wired and/or wireless communication technology, therebyexpanding the functionality of system 100.

System 100 can also include an optional display device 105 coupled tobus 110 for displaying video, graphics, and/or alphanumeric characters.It is noted that display device 105 can be a CRT (cathode ray tube), athin CRT (TCRT), a liquid crystal display (LCD), a plasma display, afield emission display (FED), video eyewear, a projection device (e.g.,an LCD (liquid crystal display) or DLP (digital light projector), amovie theater projection system, and the like), or any other displaydevice suitable for displaying video, graphics, and alphanumericcharacters recognizable to a user.

Computer system 100 of FIG. 1 further includes an optional alphanumericinput device 106 coupled to bus 110 for communicating information andcommand selections to processor(s) 101, in one embodiment. Alphanumericinput device 106 includes alphanumeric and function keys. Computer 100can also include an optional cursor control device 107 coupled to bus110 for communicating user input information and command selections toprocessor(s) 101. Cursor control device 107 can be implemented using anumber of well known devices such as a mouse, a trackball, a track pad,a joy stick, a optical tracking device, a touch screen, etc. It is notedthat a cursor can be directed and/or activated via input fromalphanumeric input device 106 using special keys and key sequencecommands. It is further noted that directing and/or activating thecursor can be accomplished by alternative means, e.g., voice activatedcommands, provided computer system 100 is configured with suchfunctionality.

FIG. 2 is a block diagram of an exemplary network 200 in whichembodiments of the present invention may be implemented. In oneembodiment, network 200 enables one or more authorized client computersystems (e.g., 210, 220, and 230), each of which are coupled to Internet201, to receive media content from a media content server 251 via theInternet 201 while preventing unauthorized client computer systems fromaccessing media stored in a database of content server 251.

Network 200 includes a web server 250 and content server 251 which arecommunicatively coupled to Internet 201. Further, web server 250 andcontent server 251 can be communicatively coupled without utilizingInternet 201, as shown. Web server 250, content server 251, and clientcomputers 210, 220, and 230 can communicate with each other. It is notedthat computers and servers of network 200 are well suited to becommunicatively coupled in various implementations. For example, webserver 250, content server 251, and client computer systems 210, 220,and 230 of network 200 can be communicatively coupled via wiredcommunication technology (e.g., twisted pair cabling, fiber optics,coaxial cable, etc.), or wireless communication technology, or acombination of wired and wireless communication technology.

Still referring to FIG. 2, it is noted that web server 250, contentserver 251, and client computer systems 210, 220 and 230 can, in oneembodiment, be each implemented in a manner similar to computer system100 of FIG. 1. However, the server and computer systems in network 200are not limited to such implementation. Additionally, web server 250 andcontent server 251 can perform various functionalities within network200. It is also noted that, in one embodiment, web server 250 andcontent server 251 can both be disposed on a single or a plurality ofphysical computer systems.

Further, it is noted that network 200 can operate with and deliver anytype of media content (e.g., audio, video, multimedia, graphics,information, data, software programs, etc.) in any format. In oneembodiment, content server 251 can provide audio and video files toclient computers 210-230 via Internet 201.

FIG. 3 is a block diagram of an exemplary copyright compliance mechanism(CCM) 300, for controlling distribution of, access to, and/or copyrightcompliance of media files, in accordance with an embodiment of thepresent invention. In one embodiment, CCM 300 contains one or moresoftware components and instructions for enabling compliance with DMCA(digital millennium copyright act) restrictions and/or RIAA (recordingindustry association of America) licensing agreements regarding mediafiles. Additionally, CCM 300's software components and instructionsfurther enable compliance with international recording restrictions suchas those defined by the IFPI (international federation of phonographicindustry), the ISRC (international standard recording industry), otherforeign or international recording associations, and/or foreign orinternational licensing restrictions. In one embodiment, CCM 300 may beintegrated into existing and/or newly developed media player andrecorder applications. In another embodiment, CCM 300 may be implementedas a stand-alone mechanism but in conjunction with existing mediaplayer/recorder applications, such that CCM 300 is communicativelycoupled to existing media player/recorder applications. Alternatively,CCM 300 can be installed as a stand-alone mechanism within a clientcomputer system 210. Additionally, CCM 300 can be installed as a standalone mechanism and/or as part of a bundled application from a mediastorage device, e.g., a CD, a DVD, an SD (secure digital card), and/oras part of an installation package. In another embodiment, CCM 300 canbe installed in conjunction with a presentation of desired mediacontent, e.g., listening to an audio file on a music CD, reading adocument, viewing a video, etc. It is noted that, in one embodiment, CCM300 may be installed on client system 210 in a clandestine manner,relative to a user.

There are currently two types of copyright licenses recognized by thedigital millennium copyright act (DMCA) for the protection ofbroadcasted copyrighted material. One of the broadcast copyrightlicenses is a compulsory license, also referred to as a statutorylicense. A statutory license is defined as a non-interactive license,meaning the user cannot select the song. Further, a caveat of this typeof broadcast license is that a user must not be able to select aparticular music file for the purpose of recording it to the user'scomputer system or other storage device. Another caveat of a statutorylicense is that a media file is not available more than once for a givenperiod of time. In one example, the period of time can be three hours.

The other type of broadcast license recognized by the DMCA is aninteractive licensing agreement. An interactive licensing agreement iscommonly with the copyright holder (e.g., a record company, the artist,etc.,) wherein the copyright holder grants permission for a server,(e.g., web server 250 and/or content server 251) to broadcastcopyrighted material. Under an interactive licensing agreement, thereare a variety of ways that copyrighted material (e.g., music files) canbe broadcast. For example, one manner in which music files can bebroadcast is to allow the user to select and listen to a particularsound recording, but without the user enabled to make a sound recording.This is commonly referred to as an interactive with “no save” license,meaning that the end user is unable to save or store the media contentfile in a relatively permanent manner. Additionally, another manner inwhich music files can be broadcast is to allow a user to not only selectand listen to a particular music file, but additionally allow the userto save that particularly music file to disc and/or burn the music fileto a CD, MP3 player, or other portable electronic device. This iscommonly referred to as an interactive with “save” license, meaning thatthe end user is enabled to save, store, or burn to CD, the media contentfile.

It is noted that the DMCA allows for the “perfect” reproduction of thesound recording. A perfect copy of a sound recording is a one-to-onemapping of the original sound recording into a digitized form, such thatthe perfect copy is virtually indistinguishable and/or has no audibledifferences from the original recording.

In one embodiment, CCM (copyright compliance mechanism) 300 can bestored in web server 250 and/or content server 251 of network 200 and isconfigured to be installed into each client computer system, e.g., 210,220 and 230, enabled to access the media files stored within contentserver 251 and/or web server 250. Alternatively, copyright compliancemechanism 300 can be externally disposed and communicatively coupledwith a client computer system 210 via, e.g., a portable media device 100a of FIG. 1. In yet another embodiment, CCM 300 can be configured to beoperable from a media storage device (e.g., 108) upon which media filesmay be disposed.

Copyright compliance mechanism 300 is configured to be operable whilehaving portions of components, entire components, combinations ofcomponents, disposed within one or more memory units and/or data storagedevices of a computer system, e.g., 210, 220, and/or 230.

Additionally, CCM 300 can be readily updated, (e.g., via Internet 201),to reflect changes or developments in the DMCA, copyright restrictionsand/or licensing agreements pertaining to any media file, changes incurrent media player applications and/or the development of new mediaplayer applications, or to counteract subversive and/or hacker-likeattempts to unlawfully obtain one or more media files. It is noted thatupdating CCM 300 can include, but is not limited to, updating portionsof components, entire components and/or combinations of components ofCCM 300.

Referring to FIG. 3, CCM 300 can include instructions 301 for enablingclient computer system 210 to interact with web server 250 and contentserver 251 of network 200. Instructions 301 enable client computersystem 210 to interact with servers, (e.g., 250 and 251) in a network,(e.g., 200).

The copyright compliance mechanism 300 also includes, in one embodiment,a user ID generator 302, for generating a user ID or user key, and oneor more cookie(s) which contain(s) information specific to the user andthe user's computer system, e.g., 210. In one embodiment, the user IDand the cookie(s) are installed in computer system 210 prior toinstallation of the remaining components of the CCM 300. It is notedthat the presence of a valid cookie(s) and a valid user ID/user key areverified by web server 250 before the remaining components of a CCM 300can be installed, within one embodiment of the present invention.Additionally, the user ID/user key can contain, but is not limited to,the user's name, the user's address, the user's credit card number, anonline payment account number, a verified email address, and an identity(username) and password selected by the user.

Furthermore, the cookie can contain, but is not limited to, informationspecific to the user, information regarding the user's computer system210, (e.g., types of media applications operational therewithin), aunique identifier associated with computer system 210, e.g., a MAC(media access control) address, an IP address, and/or the serial numberof the central processing unit (CPU) operable on computer system 210 andother information specific to the computer system and its user.

Additionally, in another embodiment, user biometrics may be combinedwith computer system 210 data and user data and incorporated into thegeneration of a user ID. Alternatively, biometric data may be used in astand-alone implementation in the generation of the user ID. Types ofbiometric data that may be utilized to provide a user ID and/orauthorization may include, but is not limited to, fingerprint data,retinal scan data, handprint data, facial recognition data, and thelike.

It is noted that the information regarding the client computer system,e.g., 210, the user of system 210, and an access key described hereincan be collectively referred to as authorization data.

Advantageously, with information regarding the user and the user'scomputer system, e.g., 210, web server 250 can determine when a user ofone computer system, e.g., 210, has given their username and password toanother user using another computer system, e.g., 220. Because theusername, password, and the user's computer system 210 are closelyassociated, web server 250 can prevent unauthorized access tocopyrighted media content, in one embodiment. It is noted that if webserver 250 detects unauthorized sharing of usernames and passwords, itcan block the user of computer system 210, as well as other users whounlawfully obtained the username and password, from future access tocopyrighted media content available through web server 250. Web server250 can invoke blocking for any specified period of time, e.g., for amatter of minutes, hours, months, years, or longer, or permanently.

Still referring to FIG. 3, copyright compliance mechanism 300 furtherincludes a coder/decoder (codec) 303 that, in one embodiment, is adaptedto perform, but is not limited to, encoding/decoding of media files,compressing/decompressing of media files, and detecting that deliveredmedia files are encrypted as prescribed by CCM 300. In the presentembodiment, coder/decoder 303 can also extract key fields from a headerattached to each media content file for, in part, verification that thefile originated from a content server, e.g., 251. It is noted that CCM300 can include one or more codecs similar to codec 303.

In the present embodiment, coder/decoder 303 can also perform a periodicand repeated check of the media file, while the media file is passed tothe media player application, (e.g., in a frame by frame basis or in abuffer by buffer basis), to ensure that CCM 300 rules are being enforcedat any particular moment during media playback. It is noted thatdiffering coder/decoders 303 can be utilized in conjunction with varioustypes of copyrighted media content including, but not limited to, audiofiles, video files, graphical files, alphanumeric files and the like,such that any type of media content file can be protected in accordancewith embodiments of the present invention.

Within FIG. 3, copyright compliance mechanism 300 also includes one ormore agent programs 304 which are configured to engage in dialogs andnegotiate and coordinate transfer of information between a computersystem, (e.g., 210, 220, or 230), a server, (e.g., web server 250 and/orcontent server 251), and/or media player applications, with or withoutrecording functionality, that are operable within a client computersystem, in one embodiment. In the present embodiment, agent program 304can also be configured to maintain system state, verify that othercomponents are being utilized simultaneously, to be autonomouslyfunctional without knowledge of the client, and can also presentmessages, (e.g., error messages, media information, advertising, etc.),via a display window or electronic mail. This enables detection ofproper skin implementation and detection of those applications that arerunning. It is noted that agent programs are well known in the art andcan be implemented in a variety of ways in accordance with the presentembodiment.

Copyright compliance mechanism 300 also includes one or more systemhooks 305, in one embodiment of the present invention. A system hook 305is, in one embodiment, a library that is installed in a computer system(e.g., 210) that intercepts system wide events. For example, a systemhook 305, in conjunction with skins 306, can govern certain propertiesand/or functionalities of media player applications operating within theclient computer system, e.g., 210, including, but not limited to, mouseclick shortcuts, keyboard shortcuts, standard system accelerators,progress bars, save functions, pause functions, rewind functions, skiptrack functions, forward track preview, copying to CD, copying to aportable electronic device, and the like.

It is noted that the term govern or governing, for purposes of thepresent invention, can refer to a disabling, deactivating, enabling,activating, etc., of a property or function. Governing can also refer toan exclusion of that function or property, such that a function orproperty may be operable but unable to perform in the manner originallyintended. For example, during the playing of a media file, the progressbar may be selected and moved from one location on the progress line toanother without having an effect on the play of the media file.

Within FIG. 3, it is further noted that codec 303 compares theinformation for the media player application operating on clientcomputer system, e.g., 210, with a list of “signatures” associated withknown media recording applications. In one embodiment, the signature canbe, but is not limited to, a unique identifier of a media playerapplication which can consist of the window class of the applicationalong with a product name string which is part of the window title forthe application. Advantageously, when new media player applications aredeveloped, their signatures can be readily added to the signature listvia an update of CCM 300 described herein.

The following C++ source code is an exemplary implementation of theportion of a codec 303 for performing media player applicationdetection, in accordance with an embodiment of the present invention. Inanother embodiment, the following source code can be modified to detectkernel streaming mechanisms operable within a client system, (e.g.,210).

int IsRecorderPresent(TCHAR * szAppClass,  TCHAR * szProdName) { TCHARszWndText[_MAX_PATH]; /* buffer to receive title string for window */HWND hWnd; /* handle to target window for operation */ int nRetVal; /*return value for operation */ /* initialize variables */ nRetVal = 0; if( _tcscmp(szAppClass, _T(“#32770”))  == 0) { /* attempt to locate dialogbox with specified window title */ if ( FindWindow((TCHAR *) 32770,szProdName)  != (HWND) 0) { /* indicate application found */ nRetVal =1; } } else { /* attempt to locate window with specified class */ if ((hWnd = FindWindow(szAppClass, (LPCTSTR) 0))  != (HWND) 0) { /* attemptto retrieve title string for window */ if ( GetWindowText(hWnd,szWndText, _MAX_PATH)  != 0) { /* attempt to locate product name withintitle string */ if ( _tcsstr(szWndText, szProdName)  != (TCHAR *) 0) {/* indicate application found */ nRetVal = 1; } } } } /* return tocaller */ return nRetVal; }

Within FIG. 3, it is further noted that codec 303 can also selectivelysuppress waveform input/output operations to prevent recording ofcopyrighted media on a client computer system, (e.g., 210). For example,codec 303, subsequent to detection of bundled media player applicationsoperational in a client computer system (e.g., 210) can stop or disruptthe playing of a media content file. This can be accomplished, in oneembodiment, by redirecting and/or diverting certain data pathways thatare commonly used for recording, such that the utilized data pathway isgoverned by the copyright compliance mechanism 300. In one embodiment,this can be performed within a driver shim, (e.g., wave driver shim 309of FIGS. 5A, 5B, 5C, and 5D.

A driver shim can be utilized for nearly any software output device,such as a standard Windows™ waveform output device (e.g., Windows™ MediaPlayer), or a hardware output device (e.g., speakers or headphones).Client computer system 210 is configured such that the driver shim(e.g., 309) appears as the default waveform media device to client levelapplication programs. Thus, requests for processing of waveform mediainput and/or output will pass through the driver shim prior to beingforwarded to the actual waveform audio driver, (e.g., media devicedriver 505 of FIGS. 5A-5D). Such waveform input/output suppression canbe triggered by other components (e.g., agent 304) of CCM 300 to beactive when a recording operation is initiated by a client computersystem (e.g., 210) during the play back of media files which are subjectto the DMCA.

It is noted that alternative driver shims can be implemented for nearlyany waveform output device including, but not limited to, a Windows™Media Player. It is further noted that the driver shim can beimplemented for nearly any media in nearly any format including, but notlimited to, audio media files, audio input and output devices, video,graphic and/or alphanumeric media files and video input and outputdevices.

The following C++ source code is an exemplary implementation of aportion of a codec 303 and/or a custom media device driver 307 fordiverting and/or redirecting certain data pathways that are commonlyused for recording of media content, in accordance with an embodiment ofthe present invention.

DWORD _stdcall widMessage(UINT uDevId,  UINT uMsg,  DWORD dwUser,  DWORDdwParam1,  DWORD dwParam2) { BOOL bSkip; /* flag indicating operation tobe skipped */ HWND hWndMon; /* handle to main window for monitor */DWORD dwRetVal; /* return value for operation */ /* initialize variables*/ bSkip = FALSE; dwRetVal = (DWORD) MMSYSERR_NOTSUPPORTED; if (uMsg ==WIDM_START) { /* attempt to locate window for monitor application */ if( (hWndMon = FindMonitorWindow( ))  != (HWND) 0) { /* obtain setting fordriver */ bDrvEnabled = ( SendMessage(hWndMon, uiRegMsg, 0, 0) == 0) ?FALSE : TRUE; } if (bDrvEnabled == TRUE) { /* indicate error inoperation */ dwRetVal = MMSYSERR_NOMEM; /* indicate operation to beskipped */ bSkip = TRUE; } } if (bSkip == FALSE) { /* invoke entry pointfor original driver */ dwRetVal = CallWidMessage(uDevId, uMsg, dwUser,dwParam1, dwParam2); } /* return to caller */ return dwRetVal; }

It is noted that when properly configured, system hook 305 can governnearly any function or property within nearly any media playerapplication that may be operational within a client computer system,(e.g., 210). In one embodiment, system hook 305 is a DLL (dynamic linklibrary) file. It is further noted that system hooks are well known inthe art, and are a standard facility in a Microsoft Windows™ operatingenvironment, and accordingly can be implemented in a variety of ways.However, it is also noted that system hook 305 can be readily adaptedfor implementation in alternative operating systems, e.g., Apple™operating systems, Sun Solaris™ operating systems, Linux operatingsystems, and nearly any other operating system.

In FIG. 3, copyright compliance mechanism 300 also includes one or moreskins 306, which can be designed to be installed in a client computersystem, (e.g., 210, 220, and 230). In one embodiment, skins 306 areutilized to assist in client side compliance with the DMCA (digitalmillennium copyright act) regarding copyrighted media content. Skins 306are customizable interfaces that, in one embodiment, are displayed on adisplay device (e.g., 105) of computer system 210 and providefunctionalities for user interaction of delivered media content.Additionally, skins 306 can also provide a display of informationrelative to the media content file including, but not limited to, songtitle, artist name, album title, artist biography, and other featuressuch as purchase inquiries, advertising, and the like.

Furthermore, when system hook 305 is unable to govern a function of themedia player application operable on a client computer system (e.g.,210) such that client computer system could be in non-compliance withDMCA and/or RIAA restrictions, a skin 306 can be implemented to providecompliance.

Differing skins 306 can be implemented depending upon the restrictionsapplicable (e.g., DMCA and/or RIAA) to each media content file. Forexample, in one embodiment, a skin 306 a may be configured forutilization with a media content file protected under a non-interactiveagreement (DMCA), such that skin 306 a may not include a pause function,a stop function, a selector function, and/or a save function, etc.Another skin, e.g., skin 306 b may, in one embodiment, be configured tobe utilized with a media content file protected under an interactivewith “no save” agreement (DMCA), such that skin 306 b may include apause function, a stop function, a selector function, and for thosemedia files having an interactive with “save” agreement, a save or aburn to CD function.

Still referring to FIG. 3, it is further noted that in the presentembodiment, each skin 306 can have a unique name and signature. In oneembodiment, skin 306 can be implemented, in part, through theutilization of an MD (message digest) 5 hash table or similar algorithm.An MD5 hash table can, in one implementation, be a check-sum algorithm.It is well known in the art that a skin, e.g., skin 306, can be renamedand/or modified to incorporate additional features and/orfunctionalities in an unauthorized manner. Since modification of theskin would change the check sum and/or MD5 hash, without knowledge ofthe MD5 hash table, changing the name or modification of the skin maysimply serve to disable the skin, in accordance with one embodiment ofthe present invention. Since copyright compliance mechanism (CCM) 300verifies skin 306, MD5 hash tables advantageously provide a deterrentagainst modifications made to the skin 306.

In one embodiment, CCM 300 also includes one or more custom media devicedriver(s) 307 for providing an even greater measure of control over themedia stream while increasing compliance reliability. A client computersystem (e.g., 210) can be configured to utilize a custom media deviceapplication (e.g., custom media device 310 of FIGS. 5B, 5C, and 5D) tocontrol unauthorized recording of media content files. A custom mediadevice application can be, but is not limited to, a custom media audiodevice application for media files having sound content, a custom videodevice application for media files having graphical and/or alphanumericcontent, etc. In one embodiment, custom media device 310 of FIG. 5B isan emulation of the custom media device driver 307. With reference toaudio media, the emulation is performed in a waveform audio driverassociated with custom media device 310. Driver 307 is configured toreceive a media file being outputted by system 210 prior to the mediafile being sent to a media output device (e.g., media output device 570)and/or a media output application (e.g., recording application 502).Examples of a media output device includes, but is not limited to, avideo card for video files, a sound card for audio files, etc. Examplesof a recording application can include, but is not limited to, CD burnerapplications for writing to another CD, ripper applications whichcapture the media file and change the format of the media file, e.g.,from a CD audio file to an .mpeg audio file, and/or a .wav file, and/oran ogg vorbis file, and various other media formats. In one embodiment,client computer system 210 is configured with a custom media devicedriver 307 emulating custom media device 310, and which is system 210'sdefault device driver for media file output. In one embodiment, anexisting GUI (graphical user interface) can be utilized or a GUI can beprovided, e.g., by utilization of skin 306 or a custom web based playerapplication or as part of a CCM 300 installation bundle, for forcing orrequiring system 210 to have driver 307 as the default driver.

Therefore, when a media content file is received by system 210 fromserver 251, the media content file is playable, provided the mediacontent file passes through the custom media device application (e.g.,310 of FIG. 5B), emulated by custom media device driver 307, prior tobeing outputted. However, if an alternative media player application isselected, delivered media files from server 251 will not play on system210.

Thus, secured media player applications would issue a media request tothe driver (e.g., 307) for the custom media device 310 which thenperforms necessary media input suppression, (e.g., waveform suppressionfor audio files), prior to forwarding the request to the defaultWindows™ media driver, (e.g., waveform audio driver for audio files).

Within FIG. 3, it is noted that requests for non-restricted media filescan pass directly through custom media device driver 307 to a Windows™waveform audio driver operable on system 210, thus reducing instances ofincompatibilities with existing media player applications that utilizewaveform media, (e.g., audio, video, etc.). Additionally, media playerapplications that do not support secured media would be unaffected. Itis further noted that for either secured media or non-restricted media,(e.g., audio media files), waveform input suppression can be triggeredby other components of CCM 300, (e.g., agents 304, system hooks 305, andskins 306, or a combination thereof), to be active when a recordingoperation is initiated simultaneously with playback of secured mediafiles, e.g., audio files. Custom device drivers are well known and canbe coded and implemented in a variety of ways including, but not limitedto, those found at developers network web sites, (e.g., a Microsoft™ oralternative OS (operating system) developer web sites).

Advantageously, by virtue of system 210 being configured with a custommedia device as the default device driver, (e.g., 310 of FIGS. 5B, 5C,and 5D), that is an emulation of a custom media device driver 307, thosemedia player applications that require their particular device driver tobe the default driver, e.g., Total Recorder, etc., are renderednon-functional for secured media. Further advantageous is that anemulated custom media device provides no native support for those mediaplayer applications used as a recording mechanism, e.g., DirectSoundcapture, (direct sound 504 of FIGS. 5A, 5B, 5C, and 5D) etc., that areable to bypass user-mode drivers for most media devices. Additionally,by virtue of the media content being sent through device driver 307,thus effectively disabling unauthorized saving/recording of media files,in one embodiment, media files that are delivered in a secured deliverysystem do not have to be encrypted, although, in another embodiment,they still may be encrypted. By virtue of non-encrypted media filesutilizing less storage space and network resources than encrypted mediafiles, networks having limited resources can utilize the functionalitiesof driver 307 of CCM 300 to provide compliance with copyrightrestrictions and/or licensing agreements applicable with a media contentfile without having the processing overhead of encrypted media files.

FIG. 4 is an exemplary system 400 for implementing a copyrightcompliance mechanism in accordance with an embodiment of the presentinvention. Specifically, system 400 illustrates web server 250, contentserver 251, or a combination of web server 250 and content server 251installing a copyright compliance mechanism (e.g., 300) in a client'scomputer system (e.g., 210) for controlling media file distribution andcontrolling user access and interaction of copyrighted media files, inone embodiment of the present invention.

Client computer system 210 can communicatively couple with a network(e.g., 200) to request a media file, a list of available media files, ora play list of audio files, e.g., MP3 files, etc. In response, webserver 250 determines if the request originates from a registered userauthorized to receive media files associated with the request. If theuser is not registered with the network, web server 250 can initiate aregistration process with the requesting client 210. Client registrationcan be accomplished in a variety of ways. For example, web server 250may deliver to client 210 a registration form having various text entryfields into which the user can enter required information. A variety ofinformation can be requested from the user by web server 250 including,but not limited to, user's name, address, phone number, credit cardnumber, online payment account number, biometric identification (e.g.,fingerprint, retinal scan, etc.), verifiable email address, and thelike. In addition, registration can, in one embodiment, include the userselecting a username and password.

Still referring to FIG. 4, web server 250 can, in one embodiment, detectinformation related to the client's computer system 210 and store thatinformation in a user/media database 450. For example, web server 250can detect a unique identifier of client computer system 210. In oneembodiment, the unique identifier can be the MAC (media access control)address of a NIC (network interface card) of client computer system 210or the MAC address of the network interface adapter integrated on themotherboard of system 210. It is understood that a NIC enables a clientcomputer system 210 to access web server 250 via a network such asInternet 201. It is well known that each NIC typically has a uniqueidentifying number MAC address. Further, web server 250 can, in oneembodiment, detect and store (also in database 450) informationregarding the type(s) of media player application(s), e.g., WindowsMedia Player™, Real Player™, iTunes Player™ (Apple), Live 365™ player,and those media player applications having recording functionality(e.g., Total Recorder, Cool Edit 2000, Sound Forge, Sound Recorder,Super MP3 Recorder, and the like) that are present and operable inclient computer system 210. In one embodiment, the client information isverified for accuracy and is then stored in a user database (e.g., 450)within web server 250.

Subsequent to registration completion, creation of the user ID andpassword, and obtaining information regarding client computer system210, all or part of this information can be installed in client computersystem 210. In one embodiment, client computer system 210 informationcan be in the form of a cookie. Web server 250 then verifies that theuser and client computer system 210 data is properly installed thereinand that their integrity has not been compromised. Subsequently, webserver 250 installs a copyright compliance mechanism (e.g., 300) intothe client's computer system, e.g., 210, in one embodiment of thepresent invention. It is noted that web server 250 may not initiateinstallation of CCM 300 until the user ID, password, and client computersystem 210 information is verified. A variety of common techniques canbe employed to install an entire CCM 300, portions of its components,entire components, and/or combinations or a function of its components.For example, copyright compliance mechanism 300 can be installed in ahidden directory within client computer system 210, thereby preventingunauthorized access to it. In one embodiment it is noted that unless CCM300 is installed in client computer system 210, its user will not beable to request, access, or have delivered thereto, media files storedby web server 250 and/or content server 251.

Referring still to FIG. 4, upon completion of client registration andinstallation of CCM 300, client computer system 210 can then request amedia play list or a plurality of play lists, etc. In response, webserver 250 determines whether the user of client computer system 210 isauthorized to receive the media play list associated with the request.In one embodiment, web server 250 can request the user's username andpassword. Alternatively, web server 250 can utilize user database 450 toverify that computer 210 is authorized to receive a media play list. Ifclient computer 210 is not authorized, web server 250 can initiateclient registration, as described herein. Additionally, web server 250can disconnect computer 210 or redirect it to an alternative web site.Regardless, if the user and client computer system 210 are notauthorized, web server 250 will not provide the requested play list toclient computer system 210.

However, if client computer system 210 is authorized, web server 210 cancheck copyright compliance mechanism 300 within data base 450 todetermine if it, or any of the components therein, have been updatedsince the last time client computer system 210 logged into web server250. If a component of CCM 300 has been updated, web server 250 caninstall the updated component and/or a more current version of CCM 300into client computer system 210, e.g., via Internet 201. If CCM 300 hasnot been updated, web server 250 can then deliver the requested mediaplay list to system 210 via Internet 201 along with an appended user keyor user identification (ID). It is noted that user database 450 can alsoinclude data for one or more media play lists that can be utilized toprovide a media play list to client computer system 210. Subsequently,the user of client computer system 210 can utilize the received mediaplay list in combination with the media player application operating onsystem 210 to transmit a delivery request for one or more desired piecesof media content from web server 250. It is noted that the deliveryrequest contains the user key for validation purposes.

Still referring to FIG. 4, upon receiving the media content deliveryrequest, web server 250 can then check the validity of the requestingmedia application and the attached user key. In one embodiment, webserver 250 can utilize user database 450 to check their validity. Ifeither or both are invalid, web server 250, in one embodiment, canredirect unauthorized client computer system 210 to an alternativedestination to prevent abuse of the system. However, if both therequesting media application and the user key are valid, CCM 300verifies that skins 306 are installed in client computer system 210.Additionally, CCM 300 further verifies that system hook(s) 305 have beenrun or are running to govern certain functions of those media playerapplications operable within client computer system 210 that are knownto provide non-compliance with one or more restricted use standards suchas the DMCA and/or the RIAA. Additionally, CCM 300 further divertsand/or redirects certain pathways that are commonly used for recording,e.g., driver 307 of FIG. 5A, device 310 of FIG. 5B, device 570 of FIG.5C, and driver 505 of FIG. 5D. Once CCM 300 has performed the abovedescribed functions, web server 250 then, in one embodiment, issues tothe client computer 210 a redirect command to the current addresslocation of the desired media file content along with an optional timesensitive access key, e.g., for that hour, day, or other definedtimeframe.

In response to the client computer system 210 receiving the redirectcommand from web server 250, the media player application operating onclient computer system 210 automatically transmits a new request and thetime sensitive access key to content server 251 for delivery of one ormore desired pieces of media content. The validity of the time sensitiveaccess key is checked by content server 251. If invalid, unauthorizedclient computer 210 is redirected by content server 250 to protectagainst abuse of the system and unauthorized access to content server251. If the time sensitive access key is valid, content server 251retrieves the desired media content from content database 451 anddelivers it to client computer system 210. It is noted that, in oneembodiment, the delivered media content can be stored in hiddendirectories and/or custom file systems that may be hidden within clientcomputer system 210 thereby preventing future unauthorized distribution.In one embodiment, an HTTP (hypertext transfer protocol) file deliverysystem is used to deliver the requested media files, meaning that themedia files are delivered in their entirety to client computer system210, as compared to streaming media which delivers small portions of themedia file.

Still referring to FIG. 4, it is noted that each media file has had, inone embodiment, a header attached therewith prior to delivery of themedia file. In one embodiment, the header can contain informationrelating to the media file, e.g., title or media ID, media data such assize, type of data, and the like. The header can also contain a sequenceor key that is recognizable to copyright compliance mechanism 300 thatidentifies the media file as originating from content server 251. In oneembodiment, the header sequence/key can also contain instructions forinvoking the licensing agreements and/or copyright restrictions that areapplicable to that particular media file.

Additionally, if licensing agreements and/or copyright restrictions arechanged, developed, or created, or if new media player applications,with or without recording functionality, are developed, CCM 300 hasappropriate modifications made to portions of components, entirecomponents, combinations of components, and/or the entire CCM 300 toenable continued compliance with licensing agreements and/or copyrightrestrictions. Furthermore, subsequent to modification of copyrightcompliance mechanism 300, modified portions of, or the entire updatedCCM 300 can be installed in client computer system 210 in a variety ofways. For example, the updated CCM 300 can be installed during clientinteraction with web server 250, during user log-in, and/or while clientcomputer system 210 is receiving the keyed play list.

Referring still to FIG. 4, it is further noted that, in one embodiment,the media files and attached headers can be encrypted prior to beingstored within content server 251. In one embodiment, the media files canbe encrypted utilizing randomly generated keys. Alternatively, variablelength keys can be utilized for encryption. It is noted that the key todecrypt the encrypted media files can be stored in database 450, contentdatabase 451 or in some combination of databases 450 and 451. It isfurther noted that the messages being passed back and forth betweenclient computer system 210 and web server 250 can also be encrypted,thereby protecting the media files and the data being exchanged fromunauthorized use or access. There are a variety of encryption mechanismsand programs that can be implemented to encrypt this data including, butnot limited to, exclusive OR, shifting with adds, public domainencryption programs such as Blowfish, and non-public domain encryptionmechanisms. It is also noted that each media file can be uniquelyencrypted, such that if the encryption code is cracked for one mediafile, it is not applicable to other media files. Alternatively, groupsof media files can be similarly encrypted. Furthermore, in anotherembodiment, the media files may not be encrypted when being delivered toa webcaster known to utilize a proprietary media player application,e.g., custom media device driver 307.

Subsequent to media file decryption, the media file may be passedthrough CCM 300, (e.g., coder/decoder 303), to a media playerapplication operating on client computer system 210, (e.g. playbackapplication 501 of FIGS. 5A, 5B, 5C, 5D, and 6A), which can then accessand utilize the delivered high fidelity media content, enabling itsuser(s) to experience the media content, e.g., listen to it, watch it,view it, or the like. In one embodiment of the present invention, aspecialized or custom media player may or may not be required toexperience the media content, (e.g., skin 306 of FIG. 3). A skin 306 maybe necessary when CCM 300 cannot modify an industry standard mediaplayer application to comply with copyright restrictions and/orlicensing agreements in accordance with the DMCA. Alternatively, anindustry standard media player can be utilized by client computer system210 to experience the media content. Typically, many media playerapplications are available and can include, but are not limited to,Windows™ Media Player™ for PCs (personal computers), iTunes™ Player orQuickTime™ for Apple computers, and XMMS player for computers utilizinga Linux operating system. Regardless of the media player applicationutilized, while the media file is passed to the media playerapplication, e.g., in a frame by frame basis or in a buffer,coder/decoder 303 will repeatedly ensure that CCM 300 rules are beingenforced at any particular moment during media playback, shown as step750 of FIG. 7C.

As the media file content is delivered to the media player application,periodically, (e.g., after a specified number of frames, after a definedperiod of time, or any desired time or data period), coder/decoder 303repeatedly determines whether or not all the rules, as defined by CCM300, are enforced. If the rules are not enforced, (e.g., a user openingup a recording application such as Total Recorder or an alternativeapplication), the presentation of the media content is, in oneembodiment, suspended or halted. In another embodiment, the presentationof the media content can be modified to output the media content in anon-audible manner, (e.g., silence). In yet another embodiment, themedia content may be audible but recording functionality can bedisabled, such that the media content cannot be recorded. Thesepresentation stoppages are collectively shown as step 751 of FIG. 7C.

If the rules in accordance with CCM 300 are enforced, the codec/decoder303 retrieves a subsequent portion of the media content that is storedlocally in client computer system 210. The newly retrieved portion ofthe media file is then presented by the client's media playerapplication. While the newly retrieved portion is presented, CCM 300again checks that the rules are enforced, and retrieves an additionalportion of the media file or suspends presentation of the media file ifthe rules are not being enforced. These operations are performedrepeatedly throughout the playback of the media file, in a loopenvironment, until the media file's contents have been presented intheir entirety. Advantageously, by constantly monitoring during playingof media files, CCM 300 can detect undesired activities and enforcesthose rules as defined by CCM 300.

FIG. 5A is an exemplary logic/bit path block diagram 500A showingutilization of a wave shim driver, (e.g., 309 of FIG. 3), in conjunctionwith copyright compliance mechanism 300, for selectively controllingrecording of copyrighted media received by a client computer system,(e.g., system 210), in one embodiment of the present invention.Copyright compliance mechanism 300 is, in one embodiment, installed andoperational on client system 210 in the manner described herein.

In one embodiment, a copyright compliance mechanism 300 is shown asbeing communicatively coupled with a media playback application 501 viacoupling 520. Therefore, CCM 300 is enabled to communicate with playbackapplication 501. In one embodiment, CCM 300 can be integrated into amedia playback application. CCM 300 is also coupled to and controls aselectable switch 311 in wave shim driver 309 (as described in FIG. 3)via coupling 522. CCM 300 is further coupled to and controls aselectable switch 511 in direct sound 504 via coupling 521. Dependingupon the copyright restrictions and licensing agreements applicable toan incoming media file, (e.g., 499), CCM 300 controls whether switches311 and 511 are open (shown), thus preventing incoming media 499 fromreaching a media recording application, or closed (not shown) to allowrecording of incoming media 499.

For example, incoming media 499 may originate from a content server,e.g., 251, coupled to system 210. In another example, incoming media 499may originate from a personal recording/electronic device, (e.g., a MP3player/recorder or similar device), coupled to system 210.Alternatively, incoming media 499 may originate from a magnetic, opticalor alternative media storage device inserted into a media device playercoupled to system 210, (e.g., a CD or DVD inserted into a CD or DVDplayer), a hard disk in a hot swappable hard drive, an SD (securedigital card) inserted into a SD reader, and the like. In yet anotherexample, incoming media 499 may originate from another media playerapplication or media recording application. Incoming media 499 may alsooriginate from a satellite radio feed (e.g., XM radio), a personalcommunication device (e.g., a mobile phone), a cable television radioinput, e.g., DMX (digital music express), a digital distribution and/ora public presentation source via a network, Internet or othercommunication connection, pay-per-view and/or pay-per-play system, or aset-top box. It is noted that incoming media 499 can originate fromnearly any source that can be coupled to system 210. However, regardlessof the source of incoming media 499, embodiments of the presentinvention, described herein, can prevent unauthorized recording of themedia 499.

FIG. 5A shows a media playback application 501, (e.g., an audio, video,or other media player application), operable within system 210 andconfigured to receive incoming media 499. Playback application 501 canbe a playback application provided by an operating system, (e.g., MediaPlayer for Windows™ by Microsoft), a freely distributed playbackapplication downloadable from the Internet, (e.g., RealPlayer orLiquidAudio), a playback application provided by a webcaster, (e.g.,PressPlay), or a playback application commercially available.

Media device driver 505 in one embodiment, may be a software driver fora sound card coupled to system 210 having a media output device 570,(e.g., speakers or headphones), coupled therewith for media files havingaudio content. In another implementation, media device driver 505 may bea software driver for a video card coupled with a display device, (e.g.,105), for displaying media files having alphanumeric and/or graphicalcontent, and so on. With reference to audio files, it is well known thata majority of recording applications assume a computer system, (e.g.,210), has a sound card disposed therein, providing full-duplex soundfunctionality to system 210. This means media output driver 505 cansimultaneously cause playback and recording of incoming media files 499.For example, media device driver 505 can playback media 499 alongwave-out line 539 to media output device 570 (e.g., speakers for audibleplayback) via wave-out line 580 while outputting media 499 on wave-outline 540 to eventually reach recording application 502.

For purposes of FIGS. 5A, 5B, 5C, and 5D, the terms wave-in line andwave-out line are referenced from the perspective of media device driver505. Additionally, for the most part, wave-in lines are depicteddownwardly and wave-out lines are depicted upwardly in FIGS. 5A, 5B, 5C,and 5D.

Continuing with FIG. 5A, playback application 501 is coupled with anoperating system (O/S) multimedia subsystem 503 via wave-in line 531.O/S multimedia subsystem 503 is coupled to a wave shim driver 309 viawave-in line 533 and wave-out line 546. O/S multimedia subsystem 503 isalso coupled to recording application 502 via wave-out line 548.Operating system (O/S) multimedia subsystem 503 can be any O/Smultimedia subsystem, e.g., a Windows™ multimedia subsystem for system210 operating under a Microsoft O/S, a QuickTime™ multimedia subsystemfor system 210 operating under an Apple O/S, and the like. Playbackapplication 501 is also coupled with direct sound 504 via wave-in line551.

Direct sound 504, in one embodiment, may represent access to a hardwareacceleration feature in a standard audio device, enabling lower levelaccess to components within media device driver 505. In anotherembodiment, direct sound 504 may represent a path that can be used by arecording application, (e.g., Total Recorder), that can be furtherconfigured to bypass the default device driver, (e.g., media devicedriver 505), to capture incoming media 499 for recording. For example,direct sound 504 can be enabled to capture incoming media 499 viawave-in line 551 and unlawfully output media 499 to recordingapplication 502 via wave-out line 568, as well as media 499 eventuallygoing to media device driver 505, the standard default driver.

Still referring to FIG. 5A, wave shim driver 309 is coupled with mediadevice driver 505 via wave-in line 537 and wave-out line 542. Mediadevice driver 505 is coupled with direct sound 504 via wave-in line 553which is shown to converge with wave-in line 537 at media device driver505. Media device driver 505 is also coupled with direct sound 504 viawave-out line 566.

Wave-out lines 542 and 566 are shown to diverge from wave-out line 540at media device driver 505 into separate paths. Wave-out line 542 iscoupled to wave shim driver 309 and wave-out line 566 is coupled todirect sound 504. When selectable switches 311 and 511 are open (shown),incoming media 499 cannot flow to recording application 502, thuspreventing unauthorized recording of it.

For example, incoming media 499 is received at playback application 501.Playback application 501 activates and communicates to CCM 300 regardingcopyright restrictions and/or licensing agreements applicable toincoming media 499. If recording restrictions apply to media 499, CCM300 can, in one embodiment, open switches 311 and 511, thereby blockingaccess to recording application 502 to effectively prevent unauthorizedrecording of media 499. In one embodiment, CCM 300 can detect if system210 is configured with direct sound 504 selected as the default driverto capture incoming media 499, via wave-in line 551, or a recordingapplication is detected and/or a hardware accelerator is active, suchthat wave driver shim 309 can be bypassed by direct sound 504. Upondetection, CCM 300 can control switch 511 such that the output path,wave-out line 568, to recording application 502 is blocked. It isfurther noted that CCM 300 can detect media recording applications anddevices as described herein, with reference to FIG. 3.

Alternatively, if media device driver 505 is selected as the defaultdriver, incoming media 499 is output from playback application 501 toO/S multimedia subsystem 503 via wave-in line 531. From subsystem 503,media 499 is output to wave shim driver 309 via wave-in line 533. Thewave shim driver 309 was described herein with reference to FIG. 3.Media 499 is output from wave shim driver 309 to media device driver 505via wave-in line 537. Once received by media device driver 505, media499 can be output via wave-out line 539 to media output device 570coupled therewith via wave-out line 580. Additionally, media devicedriver 505 can simultaneously output media 499 on wave-out line 540 backto wave shim driver 309. Dependent upon recording restrictionsapplicable to media 499, CCM 300 can, in one embodiment, close switch311 (not shown as closed), thereby allowing media 499 to be output fromwave shim driver 309 to subsystem 503 (via wave-out line 546) and thento recording application 502 via wave-out line 548. Alternatively, CCM300 can also open switch 311, thereby preventing media 499 from reachingrecording application 502.

It is noted that by virtue of CCM 300 controlling both switches 311 and511, and therefore controlling wave-out line 548 and wave-out line 568leading into recording application 502, incoming media files, (e.g.,499), can be prevented from being recorded in an unauthorized manner inaccordance with applicable copyright restrictions and/or licensingagreements related to the incoming media 499. It is also noted thatembodiments of the present invention in no way interfere with or inhibitthe playback of incoming media 499.

FIG. 5B is an exemplary logic/bit path block diagram 500B of a clientcomputer system, (e.g., 210), configured with a copyright compliancemechanism 300 for preventing unauthorized recording of copyrighted mediaaccording to an embodiment of the present invention. Copyrightcompliance mechanism 300 is, in one embodiment, coupled with andoperational on client system 210 in the manner described herein withreference to FIGS. 4, 5A, 5C, 5D, 6, and 7.

Diagram 500B of FIG. 5B is similar to diagram 500A of FIG. 5A, with afew changes. Particularly, diagram 500B includes a custom media device310 communicatively interposed between and coupled to O/S multimediasubsystem 503 and wave shim driver 309. Custom media device 310 iscoupled to O/S multimedia subsystem via wave-in line 533 and wave-outline 546. Custom media device 310 is coupled with wave shim driver 309via wave-in line 535 and wave-out line 544. Additionally, custom mediadevice 310 is coupled with direct sound 504 via wave-in line 553 whichconverges with wave-in line 533 and wave-out line 566 which divergesfrom wave-out line 546, in one embodiment.

Diagram 500B also includes a media hardware output device 570 that iscoupled to media device hardware driver 505 via line 580. Media hardwareoutput device 570 can be, but is not limited to, a sound card for audioplayback, a video card for video, graphical, alphanumeric output, andthe like.

In one embodiment, CCM 300 is communicatively coupled with playbackapplication 501 via coupling 520, waveform driver shim 309 via coupling522, and custom media device 310, via coupling 525. CCM 300 is coupledto and controls selectable switch 311 in waveform driver shim 309 viacoupling 522. CCM 300 is also coupled to and controls selectable switch312 in custom audio device 310 via coupling 525. Depending upon thecopyright restrictions and licensing agreements applicable to anincoming media file, (e.g., media 499), CCM 300 controls whetherswitches 311 and 312 are open (shown), thus preventing the incomingmedia 499 from reaching a recording application, or closed (not shown)so as to allow recording of the incoming media 499.

Continuing with FIG. 5B, direct sound 504 is coupled with custom mediadevice 310 via wave-in line 553, instead of being coupled with mediadevice driver 505 (FIG. 5A). In one embodiment, custom audio device 310mandates explicit selection through system 210, meaning that customaudio device 310 needs to be selected as a default driver of system 210.By virtue of having the selection of custom media device 310 as thedefault driver of system 210, the data path necessary for direct sound504 to capture the media content can be selectively closed.

For example, incoming media 499 originating from nearly any sourcedescribed herein with reference to FIG. 5A is received by media playbackapplication 501 of system 210. Playback application 501 communicates toCCM 300, via coupling 520, to determine whether incoming media 499 isprotected by any copyright restrictions and/or licensing agreements.Playback application 501 communicates with CCM 300 to control switch 311and 312 accordingly. For example, if recording of incoming media 499would violate applicable restrictions and/or agreements, switch 312 isin an open position (as shown), such that the output path to recordingapplication 502, (e.g., wave-out line 548 and/or wave-out line 568), iseffectively blocked thereby preventing unauthorized recording of media499.

Alternatively, if media device driver 505 is selected as the defaultdriver, incoming media 499 continues from O/S multimedia subsystem 503,through custom media device 310, wave driver shim 309, and into mediadevice driver 505 where media 499 can be simultaneously output to mediaoutput device 570 via line 580, and output on wave-out line 540 waveshim driver 309 on wave-out line 542. However, by virtue of CCM 300controlling switch 311, wave-out line 544 which eventually leads torecording application 502 is blocked, thus effectively preventingunauthorized recording of media 499.

It is noted that by virtue of CCM 300 controlling both switches 311 and312 and therefore controlling wave-out line 548 and wave-out line 568,any incoming media files, (e.g., 499), can be prevented from beingrecorded in an unauthorized manner in accordance with applicablecopyright restrictions and/or licensing agreements related to theincoming media 499.

Still referring to FIG. 5B, it is further noted that custom media device310 allows for unfettered playback of incoming media 499. Additionally,at any time during playback of media 499, custom media device 310 can bedynamically activated by CCM 300.

FIG. 5C is an exemplary logic/bit path block diagram 500C of a clientcomputer system, (e.g., 210), configured with a copyright compliancemechanism 300 for preventing unauthorized output and unauthorizedrecording of copyrighted media according to an embodiment of the presentinvention. Copyright compliance mechanism 300 is, in one embodiment,coupled with and operational on client system 210 in the mannerdescribed herein with reference to FIGS. 4, 5A, 5B, 5D, 6, and 7.

Diagram 500C of FIG. 5C is similar to diagram 500B of FIG. 5B, with afew changes. Particularly, media hardware output device 570 is shown toinclude a switch 571 controlled by CCM 300 via communication line 523,similar to switches 311 and 312, for controlling output of incomingmedia 499. Diagram 500C includes media hardware output device 570 thatis coupled with a media device driver 505. In one embodiment, mediahardware output device 570 can be a S/PDIF (Sony/Phillips DigitalInterface) card for providing multiple outputs, (e.g., an analog output573 and a digital output 575). An alternative media hardware outputdevice providing similar digital output can also be implemented asdevice 570 including, but not limited to, a USB (universal serial bus)output device and/or an externally accessible USB port located on system210, a FireWire (IEEE1394) output device and/or an externally accessibleFireWire port located on system 210, with wireline or wirelesscommunication functionality.

In one embodiment, CCM 300 is communicatively coupled with playbackapplication 501 via coupling 520, waveform driver shim 309 via coupling522, custom media device 310, via coupling 525, and media hardwareoutput device 570 via coupling 523. CCM 300 is coupled to and controlsselectable switch 311 in waveform driver shim 309 via coupling 522. CCM300 is also coupled to and controls selectable switch 312 in customaudio device 310 via coupling 525. CCM 300 is further coupled to andcontrols selectable switch 571 in media hardware output device 570 viacoupling 523. Depending upon the copyright restrictions and licensingagreements applicable to an incoming media file, (e.g., media 499), CCM300 controls whether switches 311 and 312 are open (shown), thuspreventing the incoming media 499 from reaching a recording application,or closed (not shown) so as to allow recording of the incoming media499. Additionally, CCM 300 controls whether switch 571 is open (shown),thus preventing incoming media 499 from being output from digital output575 of media hardware output device 570, or closed (not shown) to allowincoming media 499 to be output from media hardware output device 570.

By controlling media hardware output device 570, copyright compliancemechanism 300 can prevent unauthorized output of incoming media 499 to,e.g., a digital recording device that may be coupled with digital output575 of media hardware output device 570. Accordingly, in one embodiment,CCM 300 is enabled to also detect digital recording devices that may becoupled to a digital output line, e.g., 575, of a media hardware outputdevice, (e.g., 570). Examples of a digital recording device that can becoupled to media hardware output device 570 includes, but is not limitedto, mini-disc recorders, MP3 recorders, personal digital recorders,digital recording devices coupled with multimedia systems, personalcommunication devices, set-top boxes, and/or nearly any digital devicethat can capture incoming media 499 being output from media hardwareoutput device 570, (e.g., a sound card, video card, etc.).

Within FIG. 5C, direct sound 504 is shown coupled with custom mediadevice 310 via wave-in line 553, instead of being coupled with mediadevice driver 505 (FIG. 5A). In one embodiment, custom audio device 310mandates explicit selection through system 210, meaning that customaudio device 310 needs to be selected as a default driver of system 210.By virtue of having the selection of custom media device 310 as thedefault driver of system 210, the data path necessary for direct sound504 to capture the media content can be selectively closed.

For example, incoming media 499 originating from nearly any source withreference to FIG. 5A is received by media playback application 501 ofsystem 210. Playback application 501 communicates to CCM 300, viacoupling 520, to determine whether incoming media 499 is protected byany copyright restrictions and/or licensing agreements. Playbackapplication 501 communicates with CCM 300 to control switch 311, 312,and 571 accordingly. In the present example, recording of incoming media499 would violate applicable restrictions and/or agreements andtherefore switch 312 is in an open position, such that the output pathto recording application 502, (e.g., wave-out line 548 and/or wave-outline 568), is effectively blocked, thereby preventing unauthorizedrecording of media 499.

Alternatively, if media device driver 505 is selected as the defaultdriver, incoming media 499 continues from O/S multimedia subsystem 503,through custom audio device 310, wave driver shim 309, and into mediadevice driver 505 where media 499 can be simultaneously output to mediaoutput device 570 via line 580, and output on wave-out line 540 to waveshim driver 309 on wave-out line 542. However, by virtue of CCM 300controlling switch 311, wave-out line 544 which eventually leads torecording application 502 is blocked, thus effectively preventingunauthorized recording of media 499.

It is noted that by virtue of CCM 300 controlling both switches 311 and312 and therefore controlling wave-out line 548 and wave-out line 568,any incoming media files, (e.g., 499), can be prevented from beingrecording in an unauthorized manner in accordance with applicablecopyright restrictions and/or licensing agreements related to theincoming media.

Still referring to FIG. 5C, it is noted that although CCM 300 canprevent unauthorized recording of incoming media 499 by controllingswitches 311 and 312, thus preventing incoming media 499 from reachingrecording application 502, controlling switches 311 and 312 do nothingto prevent incoming media 499 from being captured by a peripheraldigital device, (e.g., a mini-disc recorder, etc.), coupled to digitaloutput 575 of device 570. Thus, by also controlling digital output 575of media hardware output device 570 via switch 571, CCM 300 can preventunauthorized capturing of incoming media 499 from output 575, (e.g., ona sound card for audio files, a video card for video and/or graphicalfiles), regardless of whether incoming media 499 is received in a secureand encrypted manner. However, when switch 571 is in a closed position,incoming media 499 may be played back in an unfettered manner.Additionally, at any time during playback of media 499, switch 312 ofcustom media device 310, switch 311 of media device driver 309, and/orswitch 571 of media hardware output device 570 can be dynamicallyactivated by CCM 300.

FIG. 5D is an exemplary logic/bit path block diagram 500D of a clientcomputer system, (e.g., 210), configured with a copyright compliancemechanism 300 for preventing unauthorized kernel based output andunauthorized recording of copyrighted media according to an embodimentof the present invention. Copyright compliance mechanism 300 is, in oneembodiment, coupled with and operational on client system 210 in themanner described herein with reference to FIGS. 4, 5A, 5B, 5C, 6, and 7.

Diagram 500D of FIG. 5D is similar to diagram 500C of FIG. 5C, with somechanges. Particularly, diagram 500D includes a kernel streamingmechanism 515, (e.g., DirectKS), that is coupled with media devicedriver 505. In one embodiment, DirectKS 515 can be used for establishinga direct connection with media device driver 505. In the presentembodiment, media device driver 505 is shown to include a switch 511controlled by CCM 300 via communication line 524, that is similar toswitches 311, 312, and 571, for controlling output of incoming media499.

In one embodiment, CCM 300 is communicatively coupled with: playbackapplication 501 via coupling 520, waveform driver shim 309 via coupling522, custom media device 310 via coupling 525, and media device driver505 via coupling 524. Specifically, CCM 300 is coupled to and controlsselectable switch 311 of waveform driver shim 309 via coupling 522. CCM300 is also coupled to and controls selectable switch 312 of customaudio device 310 via coupling 525. CCM 300 is further coupled to andcontrols selectable switch 511 of media device driver 505 via coupling524. Depending upon the copyright restrictions and/or licensingagreements applicable to an incoming media file, (e.g., media 499), CCM300 controls whether switches 311 and 312 are open (shown), thuspreventing the incoming media 499 from reaching a recording application,or closed (not shown) so as to allow recording of the incoming media499. Additionally, CCM 300 controls whether switch 511 is open (shown),thus preventing incoming media 499 from capturing incoming media 499 andredirecting it to recording application 502 to create an unauthorizedcopy or recording of incoming media 499. CCM 300 can also controlwhether switch 511 is closed (not shown) to allow DirectKS 515 tocapture and redirect incoming media 499 to recording application 502.

DirectKS 515, in one embodiment, may represent a kernel streamingmechanism that is adapted to establish a direct connection with mediadevice driver 505 of an operating system operable on client computersystem 210, enabling kernel level access to media device driver 505. Akernel streaming mechanism can be implemented for the purpose ofprecluding utilization of standard audio APIs (application programminginterfaces) to play or record media content, with particular attentionpaid to those playback applications with low latency requirements.DirectKS 515 can bypass existing APIs and communicate with media devicedriver 505. DirectKS 515 can be readily adapted to work in conjunctionwith a playback application, (e.g., 501), via coupling 581 to captureincoming media 499 and redirect it to driver 505 via coupling 583 andthen to recording application 502 via wave-out line 588. Accordingly,DirectKS 515 can be implemented to create unauthorized media recordings.

By controlling media device driver 505, copyright compliance mechanism300 can prevent unauthorized output of incoming media 499 to, e.g., adigital recording device 529 that may be coupled with recordingapplication 502. In one embodiment, media device driver 505 isconfigured through the kernel mixer (not shown) to control the datapath. Additionally, in one embodiment, CCM 300 is enabled to also detecta kernel streaming mechanism 515 (e.g., DirectKS) that may be operableon client computer system 210, as described herein with reference toFIG. 3.

In one embodiment, custom media device 310 mandates explicit selectionthrough system 210, meaning that custom media device 310 needs to beselected as a default driver of system 210. By virtue of having theselection of custom media device 310 as the default driver of system210, the data path necessary for direct sound 504 to capture the mediacontent is selectively closed.

For example, incoming media 499 originating from nearly any sourcedescribed herein with reference to FIG. 5A is received by media playbackapplication 501 of system 210. Playback application 501 communicates toCCM 300, via connection 520, to determine whether incoming media 499 isprotected by any copyright restrictions and/or licensing agreements.Playback application 501 communicates with CCM 300 to control switches311, 312, 571, and 511, accordingly. In the present example, recordingof incoming media 499 would violate applicable restrictions and/oragreements and there (e.g., wave-out line 548 and/or wave-out line 568and/or wave-out line 588), is effectively blocked, thereby preventingunauthorized recording of media 499.

Still referring to FIG. 5D, it is particularly noted that although CCM300 can prevent unauthorized recording of incoming media 499 bycontrolling switches 311, 312, and 571, thus preventing incoming media499 from reaching recording application 502, controlling switches 311,312, and 571, do nothing to prevent incoming media 499 from beingreturned to recording application 502 by a kernel streaming mechanism515 (e.g., DirectKS), which enables capturing and redirecting ofincoming media 499 to recording application 502, via wave-out line 588.Thus, by also controlling switch 511 of media device driver 505, CCM 300can prevent kernel streaming mechanism 515 from returning incoming media499 to recording application 502, thereby preventing incoming media 499from being captured and redirected to recording application 502 in anattempt to create an unauthorized copy and/or recording of incomingmedia 499. However, when switch 511 is in a closed position, incomingmedia 499 may be returned to recording application 502, such thatrecording could be possible, provided recording does not violatecopyright restrictions and/or licensing agreements applicable toincoming media 499. Additionally, at any time during playback of media499, switch 312 of custom media device 310, switch 311 of wave shimdriver 309, and/or switch 511 of media device driver 505 can bedynamically activated by CCM 300.

FIG. 6 is an block diagram of a media file, (e.g., 499), adapted to bereceived by a playback application, (e.g., 501 of FIGS. 5A-5D),configured with an indicator 605 for enabling incoming media 499 tocomply with rules according to the SCMS (serial copy management system).When applicable to a media file, e.g., 499, the SCMS allows for one copyof a copyrighted media file to be made, but not for copies of copies tobe made. Thus, if incoming media 499 can be captured by a recordingapplication, (e.g., 501 of FIGS. 5A-5D), and/or a recording device,(e.g. 529), and/or a peripheral recording device and/or a recordingapplication coupled to a digital output of a media hardware outputdevice, (e.g., digital output 575 of media hardware output device 570 ofFIGS. 5B, 5C, and 5D), and/or a kernel streaming mechanism 515, (e.g.,DirectKS 515 of FIG. 5D), unauthorized copying and/or recording may beaccomplished.

Playback application 501 is coupled with CCM 300 via communication line520 in a manner analogous to FIGS. 5A, 5B, 5C, and/or 5D. Although notshown in FIG. 6, it is noted that CCM 300 is also coupled to switches311 and 511 as shown in FIG. 5A, switches 311 and 312 in FIG. 5B,switches 311, 312, and 571 in FIG. 5C, and switches 312, 311, 571, and511, in FIG. 5D.

In one embodiment, an indicator 605 is attached to incoming media 499for preventing unauthorized copying or recording in accordance with theSCMS. In one embodiment, indicator 605 can be a bit that may betransmitted prior to beginning the delivery of incoming media 499 toplayback application 501. In another embodiment, indicator 605 may beplaced at the beginning of the bit stream of incoming media 499. In yetanother embodiment, indicator 605 may be placed within a frame period ofincoming media 499, (e.g., every fifth frame), or any other desiredframe period. In another embodiment, indicator 605 may be transmitted ata particular time interval or intervals during delivery of the mediafile, (e.g., 499). Thus, indicator 605 may be placed nearly anywherewithin or attached to the bit stream related to incoming media 499.

Within FIG. 6, indicator 605 may be comprised of various indicators,(e.g., a level 0 indicator, a level 1 indicator, and a level 2indicator), in one embodiment of the present invention. In the presentembodiment, a level 0 indicator may be for indicating to CCM 300 thatcopying is permitted without restriction, (e.g., incoming media 499 isnot copyrighted or the copyright is not asserted). In the presentembodiment, a level 1 indicator may be for indicating to CCM 300 thatone generation of copies of incoming media 499 may be made, such thatincoming media 499 is an original copy and that one copy may be made. Inthe present embodiment, a level 2 indicator may be for indicating to CCM300 that incoming media 499 is copyright protected and/or a copythereof, and as such no digital copying is permitted.

For example, incoming media 499 is received by playback application 501.Application 501 detects an indicator 605 attached therewith, in thisexample, a level 2 bit placed in the bit stream indicates to CCM 300that copying is not permitted. As such, when CCM 300 is configured insystem 210 such as that shown in FIG. 5A, in response to a level 2indicator bit, CCM 300, while controlling the media path, then activatesswitches 311 and 511 to prevent any recording of incoming media 499.

However, CCM 300 is configured in system 210 such as that shown in FIG.5B, in response to a level 2 indicator bit, CCM 300, while controllingthe media path, then activates switches 311 and 312 to prevent anyrecording of incoming media 499.

Alternatively, when CCM 300 is configured in system 210 such as thatshown in FIG. 5C, in response to a level 2 indicator bit, CCM 300, whilecontrolling the media path then activates switches 311, 312, and 571 toprevent any recording of incoming media 499.

It is noted that CCM 300 can activate or deactivate switches coupledtherewith, as described herein with reference to FIGS. 5A-5D, therebyfunneling incoming media 499 through the secure media path, in thisinstance the audio path, to prevent unauthorized copying of incomingmedia 499. It is further noted that CCM 300 can detect media recordingapplications and devices as described herein, with reference to FIG. 3.

FIGS. 7A, 7B, and 7C, are a flowchart 700 of steps performed inaccordance with one embodiment of the present invention for controllingend user interaction of delivered electronic media. Flowchart 700includes processes of the present invention which, in some embodiments,are carried out by processors and electrical components under thecontrol of computer readable and computer executable instructions. Thecomputer readable and computer executable instructions reside, forexample, in data storage features such as computer usable volatilememory 102 and/or computer usable non-volatile memory 103 of FIG. 1.However, the computer readable and computer executable instructions mayreside in any type of computer readable medium. Although specific stepsare disclosed in flowchart 700, such steps are exemplary. That is, thepresent embodiment is well suited to performing various other steps orvariations of the steps recited in FIGS. 7A, 7B, and 7C. Within thepresent embodiment, it should be appreciated that the steps of flowchart700 may be performed by software, by hardware or by any combination ofsoftware and hardware.

The present embodiment provides a method for restricting recording ofhigh fidelity media content delivered via one or more communicationnetworks. The present embodiment delivers the high fidelity mediacontent to registered clients while preventing unauthorized clients fromdirectly receiving media content from a source database. Once the clientcomputer system receives the media content, it can be stored in hiddendirectories and/or custom file systems that may be hidden to preventsubsequent unauthorized sharing with others. It is noted that variousfunctionalities can be implemented to protect and monitor the deliveredmedia content. For example, the physical address of the media contentcan be hidden from media content recipients. Alternatively, thedirectory address of the media content can be periodically changed.Additionally, an access key procedure and rate control restrictor canalso be implemented to monitor and restrict suspicious media contentrequests. Furthermore, a copyright compliance mechanism, (e.g., CCM300), can be installed in the client computer system 210 to provideclient side compliance with licensing agreements and/or copyrightrestrictions applicable to the media content. By implementing these andother functionalities, the present embodiment restricts access to andthe distribution of delivered media content and provides a means forcopyrighted media owner compensation.

It is noted that flowchart 700 is described in conjunction with FIGS. 2,3, 4, and 5A-5D, in order to more fully describe the operation of thepresent embodiment. In operation 702 of FIG. 7A, a user of a computersystem, (e.g., 210), causes the computer to communicatively couple to aweb server, (e.g., 250), via one or more communication networks, (e.g.,Internet 201), and proceeds to attempt to log in. It is understood thatthe log in process of step 702 can be accomplished in a variety of waysin accordance with the present invention.

In operation 704 of FIG. 7A, web server 250 accesses a user database,(e.g., 450), to determine whether the user and the computer system 210logging in are registered with it. If the user and computer system 210are registered with web server 250, the present embodiment proceeds tooperation 714. However, if the user and computer system 210 are notregistered with web server 250, web server 250 can initiate a user andcomputer system 210 registration process at operation 706.

In operation 706, registration of the user and computer system 210 isinitiated. The user and computer system registration process can involvethe user of computer system 210 providing personal informationincluding, but not limited to, their name, address, phone number, creditcard number, online payment account number, biometric identification(e.g., fingerprint, retinal scan, etc.), and the like. Web server 250can verify the accuracy of the information provided. Web server 250 canalso acquire information regarding the user's computer system 210including, but not limited to, identification of media players disposedand operable on system 210, a unique identifier corresponding to thecomputer system, etc. In one embodiment, the unique identifiercorresponding to the computer system can be a MAC address. Additionally,web server 250 can further request that the user of computer system 210select a username and password.

In operation 708 of FIG. 7A, subsequent to the completion of theregistration process, web server 250 generates a unique useridentification (ID) or user key associated with the user of clientcomputer system 210. The unique user ID, or user key, is then stored byweb server 250 in a manner that is associated with that registered user.Furthermore, one or more cookies containing that information specific tothat user and the user's computer system 210, is installed in anon-volatile memory device, (e.g., 103 and/or data storage device 108 ofcomputer system 210). It is noted that the user ID and cookie can bestored in a hidden directory within one or more non-volatile memorydevices within computer system 210, thereby preventing user accessand/or manipulation of that information. It is further noted that if theunique user ID, or user key, has been previously generated for the userand computer 210 that initially logged-in at operation 702, the presentembodiment proceeds to operation 714

In operation 710, web server 250 verifies that the user ID and thecookie(s) are properly installed in computer system 210 and verifies theintegrity of the cookie(s) and the user ID, thereby ensuring nounauthorized alterations to the user ID or the cookie(s) has occurred.If the user ID is not installed and/or not valid, web server 250 canre-initiate the registration process at operation 706. Alternatively,web server 250 can decouple computer system 210 from the network,thereby requiring a re-log in by the user of computer 210. If thecookie(s) and user ID are valid, the present embodiment proceeds tooperation 712.

In operation 712 of FIG. 7A, web server 250 can install a version of acopyright compliance mechanism, (e.g., 300), onto one or morenon-volatile memory devices of computer system 210. Installing CCM 300into user's computer system 210 can facilitate client side compliancewith licensing agreements and copyright restrictions applicable tospecific delivered copyrighted media content. At operation 712, thecomponents of CCM 300, such as instructions 301, coder/decoder (codec)303, agent programs 304, system hooks 305, skins 306, and custom mediadevice drivers 307 (e.g., custom media device 310 of FIGS. 5B-5D), areinstalled in computer system 210, such as that shown in FIGS. 5A-5D. Inone embodiment, a hypertext transfer protocol file delivery system canbe utilized to install CCM 300 into computer system 210. However,operation 712 is well suited to install CCM 300 on computer system 210in a wide variety of ways in accordance with the present embodiment. Forexample, CCM 300 can be installed as an integrated component within amedia player application, media recorder application, and/or mediaplayer/recorder application. Alternatively, CCM 300 can be installed asa stand-alone mechanism within client computer system 210. Additionally,CCM 300 can be installed as a stand-alone mechanism and/or as part of abundled application from a media storage device, (e.g., a CD, a DVD, anSD), and/or as part of an installation package. In another embodiment,CCM 300 can be installed in conjunction with a presentation of desiredmedia content, (e.g., listening to an audio file on a music CD, readinga document, viewing a video, etc.). It is noted that, in one embodiment,CCM 300 may be installed on client system 210 in a clandestine manner,relative to a user.

In operation 714, web server 250 can request the previously establishedusername and password of the user of client computer system 210.Accordingly, the user of client computer system 210 causes it totransmit to web server 250 the previously established username andpassword. Upon the receipt thereof, web server 250 may access a userdatabase, (e.g., 450), to determine their validity. If the username andpassword are invalid, web server 250 refuses access wherein flowchart700 may be discontinued (not shown). Alternatively, if the username andpassword are valid, the present embodiment proceeds to operation 716.

In operation 716 of FIG. 7A, web server 250 can access media filedatabase 450 to determine if copyright compliance mechanism 300 has beenupdated to reflect changes made to the DMCA (Digital MillenniumCopyright Act) and/or to the interactive/non-interactive licensingagreements recognized by the DMCA. It is noted that alternativelicensing agreements can be incorporated into copyright compliancemechanism 300. Advantageously, by providing a copyright compliancemechanism that can be readily updated to reflect changes in copyrightrestrictions, licensing agreements, and/or changes to existing mediaplayer applications, and/or the development of new media playerapplications, copyright compliance mechanism 300 can provide compliancewith current restrictions associated with the media content.

Continuing with operation 716, if web server 250 determines that CCM300, or components thereof, of computer 210 has not been updated, webserver 250 initiates installation of the newer components and/or themost current version of CCM 300 into computer system 210, shown asoperation 718. If web server 250 determines that the current version ofCCM 300 installed on system 210 does not have to be updated, the presentembodiment proceeds to operation 720 of FIG. 7B.

In operation 720 of FIG. 7B, the user of client computer system 210causes it to transmit to web server 250, (e.g., via Internet 201), arequest for a play list of available media files. It is noted that theplay list can contain all or part of the media content available from acontent server, (e.g., 251).

In operation 722, in response to web server 250 receiving the play listrequest, web server 250 transmits to client computer system 210 a mediacontent play list together with the unique user ID associated with thelogged-in user. The user ID, or user key, can be attached to the mediacontent play list in a manner invisible to the user. It is noted thatthe media content in content server 251 can be, but is not limited to,high fidelity music, audio, video, graphics, multimedia, alphanumericdata, and the like. The media content play list of operation 720 can beimplemented in diverse ways. In one example, web server 250 can generatea media content play list by combining all the available media contentinto a single play list. Alternatively, all of the media content titles,or different lists of titles, can be loaded from content server 251 andpassed to a CGI (common gateway interface) program operating on webserver 250 where the media titles, or differing lists of titles, can beconcatenated into a single dimensioned array that can be provided toclient computer system 210. It is understood that the CGI can be writtenin nearly any software computing language.

In operation 724 of FIG. 7B, the user of client computer system 210 canutilize the received media content play list in conjunction with a mediaplayer application in order to cause client computer system 210 totransmit a request to web server 250 for delivery of desired mediacontent, and wherein the user ID is automatically included therewith.The media content play list provided to client computer system 210 byweb server 250 can enable the user to create one or more customized playlists by the user selecting desired media content titles. It is notedthat a customized media play list can establish the media content thatwill eventually be delivered to client computer system 210 and the orderin which the content will be delivered. Additionally, the user of clientcomputer system 210 can create one or more customized play lists andstore those play lists in system 210 and/or within web server 250. It isnoted that a customized play list does not actually contain the desiredmedia content titles, but rather the play list includes one or moreidentifiers associated with the desired media content that can include,but is not limited to, a song, an audio clip, a video clip, a picture, amultimedia clip, an alphanumeric document, or particular portionsthereof. In another embodiment, the received media content play list caninclude a random media content delivery choice that the user of clientcomputer system 210 can transmit to web server 250, with the user ID, torequest delivery of the media content in a random manner.

In operation 726, upon receiving the request for media content fromclient computer system 210, web server 250 determines whether therequesting media application operating on client computer system 210 isa valid media application. One of the functions of a valid mediaapplication is to be a player of media content as opposed to anapplication that downloads media content in an unauthorized orunregulated manner. If web server 250 determines that the mediaapplication operating on system 210 is not a valid media application,the present embodiment proceeds to operation 727 which in oneembodiment, redirects client computer 210 to a web site where the userof system 210 can download a valid media player application or to asoftware application which can identify client computer system 210, logsystem 210 out of web server 250 and/or prevent future logging-in for adefined period of time, (e.g., 15 minutes, an hour, a day, a week, amonth, a year, or any specified amount of time). If web server 250determines that the media application operating on system 210 is a validmedia application, the present embodiment proceeds to operation 728.

In operation 728 of FIG. 7B, the present embodiment causes web server250 to determine whether the user ID (or user key) that accompanied themedia delivery request sent by client computer system 210 is valid. Ifweb server 250 determines that the user ID is invalid, the presentembodiment proceeds to operation 729 where client computer system 210can be logged off web server 250 or client computer system 210 can bereturned to operation 706 (of FIG. 7A) to re-register and to haveanother unique user ID generated by web server 250. It is noted that theorder in which operation 726 and 728 are performed can be altered suchthat operation 728 can be performed prior to operation 726. If webserver 250 determines that the user ID is valid, the present embodimentproceeds to operation 730.

In operation 730, prior to web server 250 authorizing the delivery ofthe redirect and access key for the requested media file content, shownas operation 732, CCM 300 governs certain media player applicationsand/or functions thereof that are operable on client computer system210. These governed functions can include, but is not limited to, pause,stop, progress bar, save, etc. It is noted that, in one embodiment, CCM300 can utilize system hooks 305 to accomplish the functionality ofoperation 730.

In operation 732 of FIG. 7C, the present embodiment causes web server250 to transmit to client computer system 210 a redirection commandalong with a time sensitive access key (e.g., for that hour, day or forany defined period of time) thereby enabling client computer 210 toreceive the requested media content. The redirection command can includea time sensitive address of the media content location within contentserver 251. The address is time sensitive because, in one embodiment,the content server 251 periodically renames some or all of the mediaaddress directories, thereby making previous content source addressesobsolete. Alternatively, the address of the media content is changed. Inanother embodiment, the location of the media content can be changedalong with the addresses. Regardless, unauthorized users and/orapplications are restricted from directly retrieving and/or copying themedia content from content server 251. Therefore, if someone withinappropriate or unlawful intentions is able to find where the mediacontent is stored, subsequent attempts will fail, as the previous routeno longer exists, thereby preventing future unauthorized access.

It is noted that in one embodiment of the present invention, theaddresses (or routes) of content server 251 that are actively coupled toone or more client computer systems (e.g., 210-230) are maintained whilefuture addresses, or routes, are being created for new client devices.It is further noted that as client computer systems are uncoupled fromthe media content source of content server 251, that directory address,or link, can be immediately changed, thereby preventing unauthorizedclient system or application access.

In another embodiment, the redirection of client computer system 210 tocontent server 251 can be implemented by utilizing a server networkwhere multiple servers are content providers, (e.g., 251), or by routinga requesting client computer system (e.g., 210, 220, or 230) throughmultiple servers. In yet another embodiment, the delivery of mediacontent from a central content provider (e.g., 251) can be routedthrough one or more intermediate servers before being received by therequesting client computer system, (e.g., 210).

The functionality of operation 732 is additionally well suited toprovide recordation of the Internet Protocol (IP) addresses of theclient computer systems, (e.g., 210), the media content requested andits transfer size, thereby enabling accurate monitoring of royaltypayments, clock usage and transfers, and media content popularity.

In operation 734 of FIG. 7C, upon receiving the redirection command, thepresent embodiment causes the media playback application 501 (FIGS.5A-5D) operating on client computer system 210 to automatically transmitto content server 251 a new media delivery request which can include thetime sensitive access key and the address of the desired media content.

In operation 736 of FIG. 7C, content server 251 determines whether thetime sensitive access key associated with the new media delivery requestis valid. If content server 251 determines that the time sensitiveaccess key is valid, the present embodiment proceeds to operation 738 ofFIG. 7C. However, if content server 251 determines that the time accesskey is not valid, the present embodiment proceeds to operation 737, aclient redirect.

In operation 737, content server redirects client computer 210 tooperation 732 where a new access key is generated. Alternatively,operation 737 causes the present embodiment to return to operation 704of FIG. 7A. In yet another embodiment, operation 737 can cause clientcomputer system 210 to be disconnected from content server 251.

In operation 738 of FIG. 7C, content server 251 transmits the requestedhigh fidelity media content to client computer system 210. It is notedthat each media content file delivered to client computer system 210 canhave a header attached thereto, prior to delivery, as described hereinwith reference to FIG. 4. It is further noted that both the mediacontent and the header attached thereto can be encrypted. In oneembodiment, the media content and the header can be encrypteddifferently. Alternatively, each media content file can be encrypteddifferently. In another embodiment, groups of media files areanalogously encrypted. It is noted that public domain encryptionmechanisms, (e.g., Blowfish), and/or non-public domain encryptionmechanisms can be utilized.

Still referring to operation 738, content server 251 can transmit therequested media content in a burst load (in comparison to a fixed datarate), thereby transferring the content to client computer system 210 asfast as the network transfer rate allows. Further, content server 251can have its download rate adapted to be equal to the transfer rate ofthe network to which it is coupled. In another embodiment, the contentserver 251 download rate can be adapted to equal the network transferrate of the client computer system 210 to which the media content isbeing delivered. For example, if client computer system 210 is coupledto Internet 201 via a T1 connection, then content server 251 transfersthe media content at transmission speeds allowed by the T1 connectionline. As such, once the requested media content is transmitted to clientcomputer system 210, content server 251 is then able to transmitrequested media content to another client computer system, (e.g., 220 or230). Advantageously, this provides an efficient means to transmit mediacontent, in terms of statistical distribution over time and does notoverload the communication network(s).

It is noted that delivery of the requested media content by contentserver 251 to client computer system 210 can be implemented in a varietyof ways. For example, an HTTP (hypertext transfer protocol) filetransfer protocol can be utilized to transfer the requested mediacontent as well as copyright compliance mechanism 300 to client 210. Inthis manner, the copyright compliance mechanism as well as each mediacontent file/title can be delivered in its entirety. In anotherembodiment, content server 251 can transmit to client computer system250 a large buffer of media content, (e.g., audio clips, video clips,and the like).

In operation 740 of FIG. 7C, upon receiving the requested high fidelitymedia content from content server 251, the present embodiment causesclient computer system 210 to store the delivered media content in amanner that is ready for presentation, (e.g., playback). The mediacontent is stored in client computer system 210 in a manner thatrestricts unauthorized redistribution. For example, the presentembodiment can cause the high fidelity media content to be stored in avolatile memory device (e.g., 102), utilizing one or more hiddendirectories and/or custom file systems that may be hidden, where it maybe cached for a limited period of time. Alternatively, the presentembodiment can cause the high fidelity media content to be stored in anon-volatile memory device, (e.g., 103) or data storage device (e.g.,108). It is noted that the manner in which each of the delivered mediacontent file(s) is stored, volatile or non-volatile, can be dependentupon the licensing restrictions and/or copyright agreements applicableto each media content file. It is further noted that in one embodiment,when a user of client computer system 210 turns the computer off orcauses client computer system 210 to disconnect from the network, themedia content stored in a volatile memory device is typically deletedtherefrom.

Still referring to operation 740, in another embodiment, the presentembodiment can cause client computer system 210 to store the receivedmedia content in a non-volatile manner within a media applicationoperating therein, or within one of its Internet browser applications(e.g., Netscape Communicator™, Microsoft Internet Explorer™, Opera™,Mozilla™, and the like) so that delivered media content can be used in arepetitive manner. Further, the received media content can be stored ina manner making it difficult for a user to redistribute in anunauthorized manner, while allowing the user utilization of the receivedmedia content, (e.g., by utilizing one or more hidden directories and/orcustom file systems that may also be hidden). It is noted that bystoring media content with client computer system 210 (when allowed byapplicable licensing agreements and/or copyright restrictions), contentserver 251 does not need to redeliver the same media content to clientcomputer 210 each time its user desires to experience (e.g., listen to,watch, view, etc.) the media content file.

In operation 742 of FIG. 7C, the received media content file is then fedinto a media player application (e.g., 501 of FIGS. 5A-5D), which thenruns it through a codec, (e.g., 303 of CCM 300), in one embodiment. Inresponse, coder/decoder 303 sends an authorization request to thecontent server, (e.g., 251), with attached authorization data, asdescribed herein. In response to receiving codec's 303 authorizationrequest, server 251 compares the received authorization data with thatstored in server 251, and subsequently, the present embodiment proceedsto operation 744.

In operation 744, the content server 251 responds with a pass or failauthorization. If server 251 responds with a fail, such that thereceived authorization data is invalid, the present embodiment canproceed to operation 745, where server 251 can, in one embodiment,notify the user of client system 210, (e.g., by utilization of skin306), that there was an unsuccessful authorization of the requestedmedia content file. It is noted that alternative messages having similarmeanings may also be presented to the user of client computer system210, thereby informing the user that the delivery failed. However, ifthe authorization data passes, the present embodiment proceeds tooperation 746.

In operation 746, content server 251 transmits certain data back to themedia player application enabling the media player application topresent the contents of the media file via media playback application501 of FIGS. 5A-5D. In one embodiment, a decryption key can be includedin the transmitted data to decrypt the delivered media content file. Inanother embodiment, an encryption/decryption key can be included in thetransmitted data to allow access to the contents of the media file.

In operation 748 of FIG. 7C, subsequent to media file decryption, themedia file may be passed through CCM 300, (e.g., a codec 303), to amedia player application operating on client computer system 210, (e.g.,playback application 501 of FIGS. 5A-5D), which can then access andutilize the delivered high fidelity media content, enabling its user(s)to experience the media content, (e.g., listen to it, watch it, view it,or the like). In one embodiment of the present invention, a specializedor custom media player may be involved in order to experience the mediacontent, (e.g., skin 306 of FIG. 3). Skin 306 may be implemented whenCCM 300 cannot modify an industry standard media player application tocomply with copyright restrictions and/or licensing agreements inaccordance with the DMCA. Alternatively, a specialized or custom mediaplayer may not be needed to experience the media content. Instead, anindustry standard media player can be utilized by client computer system210 to experience the media content. Typically, many media playerapplications are available and can include, but are not limited to,Windows™ Media Player™ for PCs (personal computers), iTunes™ Player orQuickTime™ for Apple computers, and XMMS player for computers utilizinga Linux operating system. Regardless of the media player applicationutilized, while the media file is passed to the media playerapplication, e.g., in a frame by frame basis or in a buffer by bufferbasis, coder/decoder 303 will repeatedly ensure that CCM 300 rules arebeing enforced at any particular moment during media playback, shown asoperation 750.

In operation 750, as the media file content is delivered to the mediaplayer application, (e.g., 501 of FIGS. 5A-5D), periodically, (e.g.,after a specified number of frames, after a defined period of time, orany desired time or data period), coder/decoder 303 repeatedlydetermines whether or not all the rules are enforced, in accordance withrules as defined by CCM 300. If the rules are not enforced, (e.g.,change due to a user opening up a recording application (e.g., TotalRecorder or alternative application)) the present method proceeds tooperation 751. If the rules, in accordance with CCM 300, are enforced,the present embodiment then proceeds to operation 752.

In operation 751 of FIG. 7C, if the rules according to CCM 300 are notenforced, the presentation of the media content is, in one embodiment,suspended or halted. In one embodiment, CCM 300 of FIG. 5A canselectively control switches 311 and 511 to prevent output of incomingmedia 499 to a recording application 502 via wave shim driver 309 anddirect sound 504 respectively, thus preventing unauthorized recording ofincoming media 499. In another embodiment, CCM 300 of FIG. 5B canselectively control switches 311 and 312 to prevent output of incomingmedia 499 to recording application 502 via wave shim driver 309 andcustom media device 310, thus preventing unauthorized recording ofincoming media 499. In yet another embodiment, CCM 300 of FIG. 5C canselectively control switches 311, 312, to not only prevent incomingmedia 499 from being recorded in an unauthorized manner but can alsoselectively control switch 571 to prevent unauthorized output ofincoming media 499 via digital output 575 of media hardware outputdevice 570. In yet another embodiment, CCM 300 of FIG. 5D canselectively control switches 311, 312, 571, and 511 to a prevent kernelstreaming mechanism 515, (e.g., DirectKS) which can establish aconnection with media device driver 505 of FIG. 5D, from capturingincoming media content and returning it to recording application tocreate an unauthorized recording of the media content. In oneembodiment, incoming media 499 may not be output from digital output575. In another embodiment, incoming media 499 may be output via digitaloutput 575 but in an inaudible manner, (e.g., silence). In yet anotherembodiment, incoming media 499 can be audible but recordingfunctionality can be disabled, such that the media content cannot berecorded.

In operation 752, if the rules are enforced in accordance with CCM 300,codec 303 retrieves a subsequent portion of the media content that isstored locally in client computer system 210. The present embodimentproceeds to operation 748 where the newly retrieved portion of the mediafile is then presented by the client's media player application. In thismanner, the playback of the media content is constantly monitored by thepresent embodiment. Advantageously, by constant monitoring playbackmedia files, CCM 300 can detect undesired activities and enforce thoserules defined by CCM 300. It is noted that process 700 can be exited(not shown) once the media file contents are presented in theirentirety.

FIG. 8 is a diagram of an exemplary high-speed global media contentdelivery system 800, in accordance with an embodiment of the presentinvention. In one embodiment, system 800 can be utilized to globallydeliver media content, (e.g., audio media, video media, graphic media,multimedia, alphanumeric media, etc.), to one or more client computersystems, e.g., 210, 220, and/or 230, in conjunction with a manner ofdelivery similar to that described herein. In one embodiment, system 800includes a global delivery network 802 that can include multiple contentservers, (e.g., 804, 806, 808, 810, 812, 814, and 816), that can belocated throughout the world and which may be referred to as points ofpresence or media delivery point(s). Each content server 804-816 canstore a portion, a substantial portion, or the entire contents of amedia content library that can be delivered to client computer systemsvia one or more networks, (e.g., LAN Internet 201, or a wide areanetwork (WAN). Accordingly, each content server 804-816 can providemedia content to client computer systems in its respective vicinity ofthe world. Alternatively, each content server can provide media contentto a substantial number of client computer systems.

For example, a media delivery point (MDP) 816, located in Tokyo, Japan,is able to provide and deliver media content from the media contentlibrary stored in its content database, (e.g., 451), to client computersystems within the Asiatic regions of the world while a media deliverypoint 812, located in New York City, N.Y., USA, is able to provide anddeliver media content from its stored media content library to clientdevices within the Eastern United States and Canada. It is noted thateach city name, (e.g., London, Tokyo, Hamburg, San Jose, Dallas,Amsterdam, or New York City), associated with one of the media deliverypoints 804-816 represents the location of that particular media deliverypoint or point of presence. However, it is further noted that these citynames are exemplary because media delivery points 804-816 can be locatedanywhere within the world, and as such are not limited to the citiesshown in global network 802.

Still referring to FIG. 8, it is further noted that global system 802 isdescribed in conjunction with FIGS. 2, 3, 4, 5A-D, and 6, in order tomore fully describe the operation of the present embodiment.Particularly, subsequent to a client computer system, (e.g., 210 of FIG.2), interacting with a web server, (e.g., 250 of FIG. 2), as describedherein, web server 250, in one embodiment, can redirect client computersystem 210 to receive the desired media content from an MDP (e.g.,804-816) based on one or more differing criteria.

For example, computer system 210 may be located in Brattleboro, Vt., andits user causes it to log-in with a web server 250 which can be locatedanywhere in the world. It is noted that operations 702-730 of FIGS. 7Aand 7B can then be performed as described herein such that the presentembodiment proceeds to operation 732 of FIG. 7C. At operation 732, thepresent embodiment can determine which media delivery points, (e.g.,804, 806, 808, 810, 812, 814, or 816), can subsequently provide anddeliver the desired media content to client computer system 210.

Still referring to FIG. 8, one or more differing criteria can beutilized to determine which media delivery point (e.g., 804-816) toselect for delivery of the desired media content. For example, thepresent embodiment can base its determination upon which media deliverypoint is in nearest proximity to client computer system 210, (e.g.,media delivery point 812). This can be performed by utilizing the storedregistration information, (e.g., address), provided by the user ofclient computer system 210. Alternatively, the present embodiment canbase its determination upon which media delivery point provides mediacontent to the part of the world in which client computer system islocated. However, if each media of the delivery points (e.g., 804-816)stores differing media content, the present embodiment can determinewhich one can actually provide the desired media content. It is notedthat these are exemplary determination criteria and the embodiments ofthe present invention are not limited to such implementation.

Subsequent to determination of which media delivery point is to providethe media content to client computer system 210 at operation 732, webserver 250 transmits to client computer system 210 a redirection commandto a media delivery point/content server, (e.g., 812), along with a timesensitive access key, also referred to as a session key, (e.g., for thathour, day, or any defined time frame) thereby enabling client computersystem 210 to eventually receive the requested media content. Withinsystem 800, the redirection command can include a time sensitive addressof the media content location within media delivery point 812.Accordingly, the New York City media delivery point 812 can subsequentlyprovide and deliver the desired media content to client computer system210. It is noted that operation 732-742 of FIG. 7C can be performed bymedia delivery point 812 in a manner similar to content server 251described herein.

Advantageously, by utilizing multiple content servers, (e.g., mediadelivery point 804-816), to provide high fidelity media content toclient computer systems, (e.g., 210-230), located throughout the world,communication network systems of the Internet 201 do not become overlycongested. Additionally, global network 802 can deliver media content toa larger number of client computer systems (e.g., 210-230) in a moreefficient manner. Furthermore, by utilizing communication technologyhaving data transfer rates of up to 320 Kbps (kilobits per second) orhigher, embodiments of the present invention provide for rapid deliveryof the media content in a worldwide implementation.

Referring still to FIG. 8, it is noted that media deliverypoints/content servers 804-816 of global network 802 can be coupled in awide variety of ways in accordance with the present embodiment. Forexample, media delivery point 804-816 can be coupled utilizing wiredand/or wireless communication technologies. Further, it is noted thatmedia delivery points 804-816 can be functionally coupled such that ifone of them fails, another media delivery point can take over andfulfill its functionality. Additionally, one or more web servers similarto web server 250 can be coupled to global network 802 utilizing wiredand/or wireless communication technologies.

Within system 800, content server/media delivery point 804 includes aweb infrastructure that, in one embodiment, is a fully redundant systemarchitecture. It is noted that each of the MDP/content servers 806-816of global network 802 can be implemented to include a web infrastructurein a manner similar to the implementation shown in MDP 804.

Specifically, the web infrastructure of media delivery point 804includes firewalls 818 and 820 which are each coupled to global network802. Firewalls 818 and 820 can be coupled to global network 802 indiverse ways, (e.g., utilizing wired and/or wireless communicationtechnologies). Particularly, firewalls 818 and 820 can each be coupledto global network 702 via a 10/100 Ethernet handoff. However, system 800is not limited in any fashion to this specific implementation. It isnoted that firewalls 818 and 820 are implemented to prevent malicioususers from accessing any part of the web infrastructure of mediadelivery point 804 in an unauthorized manner. Additionally, firewall 818can include a device 836, (e.g., a router or other switching mechanism),coupled therewith and a DB (database) server 840 coupled to device 836while firewall 820 includes a device 838, (e.g., a router or otherswitching mechanism), coupled therewith and a DB (database) server 842coupled to device 838. Furthermore, DB server 840 is coupled with device838 and DB server 842 is coupled with device 836.

Still referring to FIG. 8, and within media delivery point 804, firewall818 is coupled to a director device 822 which is coupled to internal webapplication server 826 and 828, and a hub server 830. Firewall 820 iscoupled to a director 824 which is coupled to internal web applicationservers 826 and 828, and hub server 830. Hub server 830 can beimplemented in a variety of ways including, but not limited to, as aLinux hub server. Hub server 830 is coupled to a data storage device 832capable of storing media content. Data storage device 832 can beimplemented in a variety of ways, e.g., as a RAID (redundant array ofinexpensive/independent disks) appliance.

It is noted that media delivery points 804-816 can be implemented in anymanner similar to content server 250 described herein. Additionally,media delivery points 804-816 of the present embodiment can each beimplemented as one or more physical computing devices, (e.g., computersystem 100 of FIG. 1).

In another embodiment, CCM 300 can be adapted to be disposed on a mediastorage device, (e.g., 999 of FIGS. 10 and 11). Media storage device 999can be, but is not limited to, a CD, a DVD, or other optical or magneticstorage device. By virtue of disposing a version of CCM 300 on a mediastorage device 999, embodiments of the present invention can providecopy protection for audio, video, multimedia, graphics, information,data, software programs, and other forms of media that may containcopyrighted material and which may be disposed on a media storagedevice. Alternatively, CCM 300 can be adapted to be installed on acomputer system, (e.g., 210), via a media storage device 999 upon whichit may be disposed.

FIG. 9 is a block diagram of a copyright compliance mechanism/mediastorage device (CCM/MSD) 900, a version of CCM 300 adapted to bedisposed on a media storage device, (e.g., 999 of FIGS. 10 and 11) inaccordance with an embodiment of the present invention. It is noted thatCCM 300 in CCM/MSD 900 is analogous to CCM 300 as described in FIGS. 3,4, 5A-D, 6A and 7A-C. Further, CCM/MSD 900 can be readily updated inaccordance with global delivery system 800, as described in FIGS. 7A-C.

In one embodiment, CCM/MSD 900 is adapted to provide stand-alonecompliance with copyright restrictions and/or licensing agreementsapplicable to media files that may be disposed on a media storagedevice, (e.g., 999). In another embodiment, CCM/MSD 900 is adapted to beinstalled on a computer system, (e.g., 210) to provide compliance withcopyright restrictions and/or licensing agreements applicable to mediafiles as described in FIGS. 3, 4, 5A-D, 6A and 7A-C.

Referring to FIG. 9, CCM/MSD 900 includes an autorun protocol component910 for invoking automatic installation of CCM 300. To deter users fromattempts at defeating various features inherent to CCM 300, (e.g., theautorun feature), CCM 300's monitoring program, agent program 304,verifies that those features that are to be operational are operational,and if not, CCM 300 prohibits the user from experiencing the contents ofthe media storage device.

If a user somehow defeats the autorun feature, and the user attempts toutilize an application to capture an image of the content, theapplication will make an image of the content on the media storagedevice, which also images the copyright protection contained thereon. Assuch when the image is played, CCM 300 recognizes the copy protection ispresent, and CCM 300 will only allow the user to experience the contentwhen authorized, once CCM 300 is installed.

By virtue of the protections as described above provided by CCM 300,users will be able to experience the content of the media storage devicein the content's original high quality format, thereby obviating theneed to compress the media file used on client system 210.Advantageously, the user will no longer need to suffer through poorquality output as a result of severely compressed media files.

It is noted that when adapted to be implemented in conjunction with asecure file format, meaning that the format of the file is, withoutproper authorization, non-morphogenic, embodiments of the presentinvention also provide effective compliance with copyright restrictionsand/or licensing agreements with secure files formats. CCM 300 cancontrol the types of file formats into which the media file can betransformed, (e.g., .wav, .mp3, etc.).

In one embodiment, the autorun feature associated with a media storagedevice drive, (e.g., 1112 of FIG. 10) of client system 210 is activatedand operational. Alternatively, a notice of required autorun activationwithin client system 210 may be displayed on the media storage deviceand/or the case in which the media storage device is stored.

In another embodiment, if CCM 300 is present or if the user is coupledto a server, then messages containing instructions on how to activatethe autorun feature of client system 210 may be presented to the user.

In one embodiment autorun protocol component 910 can detect mediastorage device drives resident on a computer system, (e.g., 210).

The following C++ source code is an exemplary implementation of aportion of autorun protocol component 910 for detecting media storagedevice drives residing and operable on client computer system 210,according to one embodiment of the present invention.

if ( (dwRetVal = GetLogicalDrives( )) != (DWORD) 0) { /* initializevariables */ dwMask = (DWORD) 1; /* initialize path to root of currentdrive */ _tcscpy(szDrive, _T(“A:\\”)); for (nIndex = 0, dwMask = (DWORD)1;  dwMask != (DWORD) 0;  nIndex++, dwMask <<= 1) { if ((dwRetVal &dwMask) != 0) { /* construct path to root of drive */ szDrive[0] =(TCHAR) ‘A’ + nIndex; if (GetDriveType(szDrive) == DRIVE_CDROM) {MessageBox((HWND) 0, _T(“CD-ROM drive found.”), szDrive, MB_OK); } else{ /* clear bit at current position */ dwRetVal &= (~dwMask); } } } }

In another embodiment, autorun protocol component 910 can detect whethera media storage device containing media files has been inserted into amedia storage device drive coupled with client computer system 210,(e.g., drive 1112 of FIG. 10). In another embodiment, CCM 300 caninclude instructions for monitoring media storage device drive 1112, andupon detection of drive activation, CCM 300 determines what type ofmedia storage device has been inserted therein. Subsequently, CCM 300can detect various triggers on the media storage device to invoke itsprotection, (e.g., a hidden file on newer media storage devices and/orthe copyright indicator bit on legacy media storage devices), obviatingthe need for autorun. Upon detection, CCM 300 can invoke the appropriateprotection for the associated media file.

The following C++ source code is an exemplary implementation of aportion of autorun protocol component 910 for detecting a media storagedevice inserted in a media storage device drive residing and operable onclient computer system 210, according to one embodiment of the presentinvention.

/* set error mode for operation */ uiErrMode =SetErrorMode(SEM_FAILCRITICALERRORS); /* initialize path to root ofcurrent drive */ _tcscpy(szDrive, _T(“A:\\”)); for (nIndex = 0, dwMask =(DWORD) 1;  dwMask != (DWORD) 0;  nIndex++, dwMask <<= 1) { if((dwCDROMMask & dwMask) != 0) { /* construct path to root of drive */szDrive[0] = (TCHAR) ‘A’ + nIndex; if ( GetDiskFreeSpace(szDrive,&dwSectors, &dwBytes, &dwClustersFree, &dwClusters) != 0) { /* add bitfor drive to mask */ dwRetVal |= dwMask; } } } /* restore original errormode */ SetErrorMode(uiErrMode);

Additionally, autorun protocol component 910 can also detect changes inmedia, (e.g., insertion of a different media storage device 999).Further, other media changes can be detected subsequent to adaptation ofthe source code including, but not limited to, detecting a previouslyaccessed media file and/or detecting a previously inserted media storagedevice.

The following C++ source code is an exemplary implementation of aportion of autorun protocol component 910 for detecting a change inmedia, according to one embodiment of the present invention.

 /* initialize path to root of current drive */ _tcscpy(szDrive,_T(“A:\\”)); for (nIndex = 0, dwMask = (DWORD) 1;  dwMask != (DWORD) 0; nIndex++, dwMask <<= 1) { /* check for presence of CD-ROM media indrive */ if ((dwCurrMask & dwMask) != 0) { /* check if media previouslyin drive */ if ((dwPrevMask & dwMask) == 0) { /* construct path to rootof drive */ szDrive[0] = (TCHAR) ‘A’ + nIndex; /* check for presence ofmarker on drive */ if (IsMPBMarkerPresent(szDrive) != 0) { /* processautorun information present on drive */ nRetVal =ProcessAutorun(szDrive); } } } }

Still referring to FIG. 9, CCM/MSD 900 also includes a kernel levelfilter driver 920 for controlling a data input path of an operatingsystem coupled with and operable on client computer system 210.

CCM/MSD 900 also includes a generalized filter driver 930 forcontrolling ripping and “burning” applications, (e.g., Nero, Roxio,Exact Audio Copy, and others), thereby preventing such activities.

The following C++ source code is an exemplary implementation of aportion of generalized filter driver 930 for controlling ripping andburning applications that may be residing on and operable within clientcomputer system 210, in accordance with one embodiment of the presentinvention.

bool bDisabled;  /* flag indicating CD reads disabled */ /* initializevariables */ bDisabled = false; if (bProtected == true) { if (type ==IRP_MJ_DEVICE_CONTROL) { ULONG ulIoControlCode =stack− >Parameters.DeviceIoControl.IoControlCode; if (ulIoControlCode ==IOCTL_SCSI_PASS_THROUGH) { SCSI_PASS_THROUGH * pspt = (SCSI_PASS_THROUGH*) Irp−>AssociatedIrp.SystemBuffer; if ( (pspt != NULL) && (pspt−>Cdb[0]== SCSIOP_READ_CD)) { pspt−>DataTransferLength = 0; pspt−>ScsiStatus =0; bDisabled = true; } } else if (ulIoControlCode ==IOCTL_SCSI_PASS_THROUGH_DIRECT) { SCSI_PASS_THROUGH_DIRECT * psptd =(SCSI_PASS_THROUGH_DIRECT *) Irp−>AssociatedIrp.SystemBuffer; if ((psptd != NULL) && (psptd−>Cdb[0] == SCSIOP_READ_CD)) {psptd−>DataTransferLength = 0; psptd−>ScsiStatus = 0; bDisabled = true;} } } } if (bDisabled == true) { /* complete current request */ status =CompleteRequest(Irp, STATUS_SUCCESS, 0); } else { /* pass request downwithout additional processing */ status =IoAcquireRemoveLock(&pdx−>RemoveLock, Irp); if (!NT_SUCCESS(status))return CompleteRequest(Irp, status, 0);IoSkipCurrentIrpStackLocation(Irp); status =IoCallDriver(pdx−>LowerDeviceObject, Irp);IoReleaseRemoveLock(&pdx−>RemoveLock, Irp); }

Still referring to FIG. 9, CCM/MSD 900 includes a CCM 300, analogous toCCM 300 of FIG. 3, that is adapted to be installed in client computersystem 210 in one or more ways described herein.

In one embodiment, kernel level filter driver 920, generalized filterdriver 930 and CCM 300 of CCM/MSD 900 are automatically installed onclient computer system 210, subsequent to insertion of media storagedevice 999 into a media storage device drive, (e.g., 1112 of FIGS. 10and 11. Autorun protocol component 910, as described above, detectsinsertion of media storage device 999 into an appropriate drive, andinitiates installation of the components, (e.g., CCM 300, driver 920 anddriver 930). In one embodiment, drivers 920 and 930 may be temporarilyinstalled and may be deleted upon removal of media storage device 999from media storage device drive 1112. In yet another embodiment, drivers920 and 930 may be installed in hidden directories and/or files withinclient computer system 210. In another embodiment, some components ofCCM 300 can remain installed on client system 210, (e.g. the monitoringprogram (agent program 304). In still another embodiment, othercomponents, (e.g., the kernel level filter driver 920), can bedynamically loaded and unloaded as necessary in accordance withcopyright restrictions and/or licensing agreements applicable to themedia file.

Embodiments of the present invention utilize software, (e.g., CCM/MSD900), that is placed on media storage device 999, in conjunction withcontrolling software CCM 300 installed on client computer system 210,and web server 250 and/or content server 251, wherein each component iscommunicatively coupled with the other via the Internet, therebyenabling dynamic updating of CCM 300 in the manner as described withreference to FIG. 4, and operation 716 and 718 of FIGS. 7A-C.

In the present embodiment, CCM/MSD 900 provides a stand alone DRM thatis far more sophisticated than existing DRM solutions. This is becauseCCM/MSD 900 goes into the data pathway of the operating system operableon client computer system 210 and obtains control of the data pathway,(e.g., filter driver 1108 of FIG. 11), rather than exploitinginefficiencies or errors in the computer system.

FIG. 10 is a block diagram of a communicative environment 1000 forcontrolling unauthorized reproduction of protected media files disposedon a media storage device in accordance with an embodiment of thepresent invention. Included in communicative environment 1000 is a mediastorage device drive 1112 coupled with a client computer system 210 viaa data/address bus 110. Client computer system 210 is coupled with webserver 250 and content server 251 via Internet 201. A media storagedevice 999, upon which a CCM/MSD 900 may be disposed, can be inserted inmedia storage device drive 1112. As such, autorun protocol component 910detects the insertion and automatically invokes installation of CCM 300,kernel level filter driver 920 and generalized filter driver 930 frommedia storage device 999 into client computer system 210. Subsequent toinstallation, CCM 300 initiates a dynamic update with web server 250and/or content server 251, via Internet 201. By installing CCM 300 onclient computer system, agent program 304 (FIG. 3) of CCM 300 is able tocontrol the integrity of the software associated with CCM/MSD 900.Additionally, by conferring with servers 250 and/or 251 via Internet 201online, the CCM 300 software version on media storage device 999 andinstalled on client computer system 210 can be updated whencircumventions occur and/or kept current from platform to platform.

Advantageously, the monitoring mechanism of agent program 304 enablesconstant morphing of the version of CCM 300 disposed on media storagedevice 999 by communicating with server 250 and/or 251 and utilizing thedynamic update capabilities of global network 800 to readily update thatwhich has been installed on client computer system 210, via mediastorage device 999.

In one embodiment, the installation is performed clandestine withrespect to the user and is initiated by inserting media storage device999 into an appropriate media storage device drive, (e.g. amagnetic/optical disk drive or alternative device drive coupled withclient system 210). If the user is not registered with CCM 300, asdescribed herein with reference to FIG. 4 and FIGS. 7A-7C, onceinstalled, CCM 300 initiates an update process with web server 250and/or content server 251 to readily include updates that have beeninvoked subsequent to release of the media file on media storage device999. By virtue of the dynamic update capabilities of CCM 300, regardlessof the version of CCM 300 on media storage device 999, CCM 300 providescompliance with copyright restrictions and/or licensing agreementsapplicable to the media file on media storage device 999.Advantageously, enabling dynamic adaptability of CCM 300 provides forcontinued interoperability with new and updated operating systems,advancements in electronic technology, communication technologies andprotocols, and the like, ensuring the effectiveness of CCM 300 into thefuture.

In another embodiment, if the user is a registered user with globaldelivery system 800, CCM 300 can detect which version is most current.Accordingly, when the version existing on client system 210 is morecurrent that the version (for install) on media storage device 999, CCM300 can bypass the install process and present the contents contained onmedia storage device 999 to the user for them to experience.

Further advantageous, this technology is backward compatible with mediastorage device drives manufactured subsequent to and including the year1982. Additionally, CCM 300 is compatible with media storage deviceshaving a copyright indicator bit disposed thereon. The copyrightindicator bit has been included on all CDs released since the year 1982.

In the present embodiment of FIG. 10, the media content is not encryptedon media storage device 999. In one embodiment, if the media content isencrypted on computer 210, it can be decrypted on the computer 210.However, home players and/or stand alone media playing devices rarelyinclude a decryption mechanism, and to experience the music on a homemachine, the music is conventionally not encrypted.

In one embodiment, an additional component of CCM 300 is that thetrigger for agent program 304 may be the copyright bit indicator. Thismeans when the copyright indicator bit is detected by CCM 300, thefunctions of CCM 300 are initiated. Alternatively, in anotherembodiment, when the copyright bit indicator is not detected, CCM 300may remain in an un-invoked or idle state. If CCM 300 can detect thecopyright bit indicator, CCM 300 can provide the appropriate compliancewith regard to copyright restrictions and/or licensing agreementsapplicable to the media files.

In an alternative embodiment, a trigger control in the table of contentsof media storage device 999 includes instructions for triggering autorunprotocol 910 of CCM/MSD 900 and can utilize the copyright indicator bitor alternative implementation to trigger the technology. In this manner,CCM 300 can control copyrighted works while public domain material canbe experienced and reproduced at a user's discretion. Because autoruncan be problematic for media storage device manufacturers, embodimentsof CCM/MSD 900 can include alternative autorun programs that performanalogous to autorun.

In another embodiment, CCM 300 can invoke its own proprietary player,(e.g., custom media device 310 as described with reference to FIG. 3),thus enabling increased control of copyright restrictions and/orlicensing agreements applicable to the media. By invoking custom mediadevice 310, CCM 300 enables user experience of the media while providingprotection against unauthorized reproduction of the media disposed onmedia storage device 999.

In an alternative embodiment, the media files and the CCM/MSD 900disposed on a media storage device 999 are encrypted. Thisimplementation is particularly advantageous for demonstration (demo)versions of media files, beta test versions, and the like that may bedisposed on media storage device 999. It is noted that the presentembodiment is operable in an online environment, meaning that clientcomputer system 210 is communicatively coupled with web server 250and/or content server 251 to enable a user experience of the content ona demo version of media storage device 999. In this implementation, CCM300 allows for specific plays for specific users, which can becontrolled via a network, (e.g., network 1000 of FIG. 10), and server250 and/or 251.

In another embodiment, CCM 300 can be implemented for demo and/orpre-release protection. In this embodiment, CCM 300 utilizessophisticated encryption technology to encrypt the table of contents andCCM 300 with an associated decrypted key located on client computersystem 210. Encrypting CCM 300 can also deter nefarious attempts toreverse engineer CCM 300. Decryption can be performed using anassociated decryption key. Alternatively, decryption can be performed bya proprietary or custom media player application resident on demo mediastorage device, (e.g., 999).

The content of media storage device 999 is encrypted, using variouslevels of encryption to provide protection levels commensurate withcopyright holder's desires and required protection. For example, mediastorage device 999 is delivered to a user or critic for the purposes ofreview, the user inserts media storage device 999 into the appropriatestorage device reader or connector coupled with the journalist'scomputer (e.g., 210), and CCM 300 is installed on client system 200 in amanner clandestine to the user. Once installed, CCM 300 initiates acommunication session with web server 250/content server 251, wherecontent server 251 can provide authorization for the user to experiencethe media on media storage device 999.

Accordingly, if the user, to whom demo media storage device 999 had beenreleased, had demo media storage device 999 stolen, or if the userallowed alternative parties to try to experience the content of mediastorage device 999, the unauthorized party would have to try to crackthe encryption keys and the encryption of the actual content of mediastorage device 999, consuming non-trivial amounts of time.

Thus, CCM 300 is able to control which users receive authorization toexperience the media of media storage device 999, how many times theuser may experience the media, and CCM 300 may also define a period oftime until the media may no longer be accessible. This may enablecopyright holders to release the content on an authorized media storagedevice, (e.g., 999), prior to “pirated” copies flooding the market.

Accordingly, a demo media storage device 999 may be configured such thata first user may get a copy, a second user may get a copy, and if it isknown that the second user will share the demo with a third and a fourthuser, then the known users would be enabled to experience the media.Advantageously, by virtue of defining which users can access andexperience the media, any unauthorized sharing of the media by one ofthe authorized users can be readily detected, and further sharing orexperiencing of the media may be halted. Additionally, because theauthorized user shared the media in an unauthorized manner, in a worsecase scenario, criminal charges could be filed against that user.

It is noted that placing CCM/MSD 900 on a media storage device, (e.g.,999), so as to enable installation of CCM 300 on client system 210 isone manner in which CCM 300 can be installed on client system 210. Analternative manner in which CCM 300 can be installed on client computersystem 210 is through “cross-pollination.” For example, webcastersbroadcast the media file to the user. The media file has a CCM 300coupled with the media file, and upon downloading the media file ontoclient computer system 210, embodiments of the present invention enablethe installation of CCM 300 onto client computer system 210. In anothermanner, CCM 300 is incorporated into and becomes part of an operatingsystem operational on client system 210. Alternatively, laws are passedthat mandate the inclusion of CCM 300 on each client computer system210.

FIG. 11 is an exemplary logic/bit path block diagram 1100 of a clientcomputer system, (e.g., 210), configured with a copyright compliancemechanism (CCM) 300 for preventing unauthorized reproduction ofcopyrighted media according to an embodiment of the present invention.Copyright compliance mechanism 300 is, in one embodiment, coupled withand operational on client system 210 in any manner similar to thatdescribed herein with reference to FIGS. 4, 5A-5D, 6A, 7A-7C, 9, and 10.

Diagram 1100 of FIG. 11 includes a media storage device mediaextraction/creation application 1102 communicatively coupled tooperating system input/output subsystem 1104 via wave in line 1121 andwave out line 1138. Operating system input/output subsystem 1104 iscoupled with media storage device class driver 1106 via wave in line1123 and wave out line 1136. Media storage device class driver 1106 iscoupled with filter driver 1108 via wave in line 1125 and wave out line1134. Filter driver 1108 is coupled with media storage device portdriver 1110 via wave in line 1127 and wave out line 1132. Filter driver1108 is shown to include a switch 1111, controlled by CCM 300 viacoupling 1160. Media storage device port driver 1110 is coupled withmedia storage device drive 1112 via wave line in 1129 and wave line out1130. Media storage device 999, shown to include CCM/MSD 900 isreceivable by media storage device drive 1112. Additionally, CCM 300 iscoupled with operating system input/output subsystem 1104 via wave inline 1150 and wave out line 1151.

In one embodiment, CCM 300 is coupled to and controls selectable switch1111 in filter driver 1108. Depending upon the copyright restrictionsand/or licensing agreements applicable to a media file disposed on mediastorage device 999, CCM 300 controls whether switch 1111 is open(shown), thus preventing the media file from reaching mediaextraction/creation application 1102, or closed (not shown) so as toallow reproduction of the protected media file. Mediaextraction/creation application 1102 can be a “ripping” or “burning”application such as Nero, Roxio, Exact Audio Copy, or other readilyavailable application.

Continuing with FIG. 11, media storage device 999 is received by mediastorage device drive 1112. CCM 300 determines whether media storagedevice 999 or media disposed thereon is protected by any copyrightrestrictions and/or licensing agreements, e.g., via detection of acopyright indicator bit. CCM 300 communicates with filter driver 1108 tocontrol switch 1111 accordingly. In the present example, reproducingmedia storage device 999, and/or the contents thereon, would violateapplicable restrictions and/or agreements and therefore switch 1111 isin an open position such that the output path, (e.g., wave-out line1138) to media extraction/creation application 1102 is effectivelyblocked thereby preventing unauthorized reproduction of media storagedevice 999.

It is particularly noted that by virtue of CCM 300 controlling switch1111, and therefore controlling wave-out line 1138, any incomingcopyright protected media disposed on a media storage device 999 can beprevented from being reproduced in an unauthorized manner in accordancewith applicable copyright restrictions and/or licensing agreementsrelated to the incoming media.

Advantageously, as new secure or proprietary file formats are developed,CCM 300 can be readily adapted to be functional therewith. Further,CCM/MSD 900 can prevent users from making unauthorized reproductions(e.g., recording, copying, ripping, burning, etc.) of media files. Byusing kernel level filter drivers (e.g., 1108) and getting to a lowenough level within the operating system (OS) on client system 210, CCM300 can detect particular applications and when they request mediastorage device drive 1112 to poll the media file for copying, ripping,etc., and disable the data input path. CCM 300, in this embodiment,deals with the input pathway.

In one embodiment, alternative applications that monitor the state ofclient computer system 210 can enable the autorun functionality ofclient computer system 210 or alternatively, invoke an automaticmechanism similar to autorun to ensure invocation of CCM 300 forcompliance of copyright restrictions and/or licensing agreementsapplicable to media storage device 999 and/or the copyright protectedmedia disposed thereon.

In one embodiment, CCM 300 can invoke a proprietary media player frommedia storage device 999, or activate a proprietary media playerresident and operable on client computer system 210, or an alternativeauthorized media player resident on client computer system 210, in amanner similar to that described herein with reference to FIG. 3.

When media storage device 999 is a multisession device, e.g., a compactdisk having a data session and a music session (audio tracks), and it isinserted into or communicatively coupled with media storage device drive1112 such that its content is accessible, CCM 300 views the contents ofthe media storage device 999, and in some operating systems the audiotracks will not be displayed. Instead, the data session is shown, as isan autorun file, (e.g., autorun protocol component 910), and uponclicking, invokes a player application. CCM 300 can have a data sessionand files to which a user may not have access unless a playerapplication is invoked.

In one embodiment, the player application could deposit a monitoringportion (e.g., agent program 304) on client system 210, which in oneembodiment may reside on client computer system 210 subsequent toremoval or decoupling of media storage device 999 from media storagedevice drive 1112.

By virtue of content in a multisession media storage device 999, whichmay not be directly accessible to most player applications, the playerapplication can be invoked which can then install the CCM 300 intoclient system 210, according to one embodiment of the present invention.

In one embodiment, a proprietary media player application is stored onmedia storage device 999. However, it may not be automatically invoked.Upon some user intervention, e.g., inserting media storage device 999into media storage device drive 1112, the media player application isloaded onto client system 210 which has CCM 300 integrated therewith.Thus, CCM 300 is launched regardless of autorun being activated orde-activated, and mandates the user to utilize the proprietary mediaplayer application, to experience the content of the media, (e.g., mediafiles), on the media storage device 999.

In an alternative embodiment, client computer system 210 has autorunturned off, wherein it is common for the user to be unable to play amedia file unless a proprietary media player application is invoked.Activating the proprietary media player application can initiate aninstallation of those components of CCM 300 that are bypassed whenautorun is not active.

Advantageously, by providing a copyright compliance mechanism, (e.g.,300), which can be easily and readily installed on a client computersystem, (e.g., 210) one of more embodiments of the present invention canbe implemented to control access to, the delivery of, and the user'sexperience with media content subject to copyright restrictions and/orlicensing agreements, for example, as defined by the DMCA. Additionally,by closely associating a client computer system, (e.g., 210), with theuser thereof and the media content received, embodiments of the presentinvention can provide for accurate royalty recording.

FIG. 12 is a block diagram of a usage compliance mechanism 1200, analternative version of copyright compliance mechanism 300 which isconfigured to be disposed on a media storage device, (e.g., 999 of FIGS.10, 11, 13, 14, and 15) in accordance with an embodiment of the presentinvention. It is noted that CCM 300 of usage compliance mechanism 1200is similar to CCM 300 as described herein with reference to FIGS. 3, 4,5A-5D, 6A, 7A-7C, 8, 9, 10, and 11. Further, usage compliance mechanism1200 can be readily updated in accordance with global delivery system800, in a manner similar to that described herein with reference toFIGS. 7A-7C.

In one embodiment, usage compliance mechanism 1200 can be disposed on amedia storage device, (e.g., 999). Content disposed thereon can, in oneembodiment, be demonstration and/or pre-release content. Examples ofdemonstration and/or pre-release content can include, but is not limitedto, audio, video, multimedia, graphics, information, data, softwareprograms, etc. More specifically, demonstration and/or pre-releasecontent can contain, but is not limited to, digital movies or music thatmay be distributed to persons in the related media field for review,(e.g., a motion picture academy member for their review of a movie, arecord industry critic to review songs that may be released on a newcompact disc, etc.). Alternatively, demonstration and/or pre-releasecontent can also contain, but is not limited to, a beta version of asoftware program, and the like.

Alternatively, the content disposed on media storage device 999 can, inanother embodiment, be a commercial release of audio content, videocontent, software application, etc. Embodiments of the present inventionare well suited to be implemented in a commercial environment, e.g.,public presentation systems such as those in movie theaters,auditoriums, arenas and the like. Additionally, embodiments of thepresent invention are readily adaptable to be implemented in commercialdistribution points, e.g., audio, video, and/or software retail and/orrental establishments, as well as for pay-per-view and/or pay-per-playimplementations.

Further, literary works, documents, graphics such as pictures, painting,drawing, and the like can comprise the content on media storage device999. It is noted that a nearly endless variety of demonstration,pre-release, and/or commercially released content can be disposed onmedia storage device 999.

Referring to FIG. 12, usage compliance mechanism (UCM) 1200 includes anautorun protocol 910 for invoking installation of components of UCM 1200on a client computer system, (e.g., 210), in one embodiment of thepresent invention. Autorun protocol 910 of FIG. 12 is analogous toautorun protocol 910 of FIG. 9. Also included in UCM 1200 is a filesystem filter driver 1220, in one embodiment of the present invention.

File system filter driver 1220 can, in one embodiment, be an upper leveland/or lower level filter for the individual bus devices within clientcomputer system 210, e.g., media storage device drive 1112 of FIGS. 10,11, 13, 14, and 15. File system filter driver 1220 is enabled to hookonto access to a media storage device drive 1112, (e.g., a CD drive),and intercept data reads associated with accessing the content on mediastorage device 999.

File system filter driver 1220 includes a decrypter 1221 for providingdecryption of encryptions applied to encrypted content, (e.g.,encryptions 2351-P applied to encryptions 1351-N of media content 2001-Mof FIG. 13), in one embodiment of the present invention. Decrypter 1221can provide dynamic decryption of encryptions applied to encrypted mediacontent on a media storage device 999 as the content, (e.g., 2001-M), isaccessed and read by media storage device drive 1112.

Still referring to FIG. 12, UCM 1200 also includes a secure media player1210. Secure media player 1210 can be, in one embodiment, similar tocustom media device 310, that is an emulation of the custom media devicedriver 307, as described herein with reference to FIGS. 3 and 5B-5D.Alternatively, secure media player 1210 may be an alternative mediaplayer having controlling properties analogous to custom media device310. Secure media player 1210 includes a decrypter 1211 for decryptingencryption applied to each instance of media disposed on a media storagedevice 999, e.g., encryptions 1351 to 1N applied to media content 2001to N of FIG. 13, respectively. Secure media player 1210 also includes awatermarker 1212 for watermarking the outgoing data stream. In oneembodiment, watermarker 1212 operates concurrent with secure mediaplayer 1210 and during player 1210 rendering of the content. Forexample, watermarker 1212 can attach a serial number, e.g., serialnumber 1380 of FIG. 13, associated with each media storage device 999onto the outgoing data stream.

FIG. 13 is a block diagram of contents and components that may bedisposed on a media storage device, (e.g., 999), in accordance withembodiments of the present invention. Device 999 is shown with multipleinstances of content, (e.g. media content 2001-M), disposed thereon.Media content 2001-M may be, but are not limited to, movies, audiotracks, software, beta software, documents, literary works, etc. It isnoted that any digital media can be disposed on media storage device 999or on a plurality of media storage devices 999.

Media storage device 999 of FIG. 13 is analogous to media storage device999 of FIGS. 10, 11, 14, and 15. In one embodiment of the presentinvention, media storage device 999 is configured for utilization inconjunction with demonstration and/or pre-release content.

Media storage device 999 of FIG. 13 is shown to have disposed thereon aUCM (usage compliance mechanism) 1200 for controlling presentation ofcontent, (e.g., media content 2001-M), disposed on media storage device999. The UCM 1200 described herein with reference to FIGS. 13, 14, and15, is analogous to the UCM 1200 described herein with reference to FIG.12. It is noted that autorun protocol 910 of UCM 1200 is, in oneembodiment, disposed on media storage device 999 in a non-encryptedformat.

Also shown on media storage device 999 is a unique identifier 1380,(e.g., a serial number), for providing a unique identification of themedia storage device, in one embodiment of the present invention. Uniqueidentifier 1380 may be, but is not limited to, nearly anydistinguishable identifying type of indicator, (e.g., a randomlygenerated number, a sequential number, a combination of numbers andalphanumeric characters, and the like).

Advantageously, by disposing unique identifier 1380 on a media storagedevice 999, it enables close association of the content disposedthereon, (e.g., media content 2001-M), with the anticipated recipient,(e.g., a movie critic, a music critic, an academy award member, asoftware beta tester, etc.), of the media storage device. Therefore, byclosely associating a media storage device, (e.g., 999), with ananticipated recipient, (e.g., the user of computer system 210),embodiments of the present invention can prevent unauthorized personsfrom experiencing content on a media storage device, as described hereinwith reference to FIGS. 3, 4, 7A-7C, and 8.

Further advantageous is that by having unique identifier 1380 for eachmedia storage device 999, embodiments also provide security at the mediastorage device mastering level. This means that an employee working at amastering facility who dishonestly and/or unlawfully purloins a copy ofthe media storage device is prevented from copying the contents andturning it into bootleg (unauthorized versions) copies of the mediastorage device in an attempt to flood the market. Specifically, byvirtue of each media storage device 999 having unique identifier 1380,and each media storage device 999 is associated with its intendedrecipient, persons not associated with a particular media storage device999 are unable to experience the content thereon. It is noted that whilethe market may still be flooded with bootleg copies, those that acquirea bootleg copy of a media storage device 999, in accordance with thepresent invention, will not be able to experience the content thereon,thereby possibly causing the public to be less receptive to the idea ofan inexpensive bootleg copy of something that they cannot use.

In one embodiment, media storage device 999 may be distributed to itsintended recipients in a variety of ways. For example, distribution ofmedia storage device 999 to its intended recipients can include, but isnot limited to, postal delivery methods, e.g., the United States PostalService, parcel delivery services such UPS (United Parcel Service)and/or Federal Express, courier delivery services, and the like. Inanother embodiment, the intended recipient of a media storage device 999may be required to physically pick up device 999 from a distributionpoint.

Media storage device 999 can include multiple instances of content,e.g., media content 2001-M, in one embodiment of the present invention.Media content 2001-M can be any type of digital media content,including, but not limited to, audio, video, multimedia, graphics,information, data, software programs, etc.

Still referring to FIG. 13, in one embodiment of the present invention,each instance of media 2001-M is subject to a first encryption, e.g.,encryptions 1351-N, respectively. In one embodiment, a first decryptionkey for each encryption, e.g., encryptions 1351-N, may be stored in aserver, (e.g., web server 250 and/or content server 251 of FIGS. 2, 4,10, and 14). In one embodiment, secure media player 1210 can utilizedecrypter 1211 and the decryption key stored on web server 250 and/orcontent server 251 to decrypt encryptions 1351-N during rendering of thecontent. It is noted that secure media player 1210 can becommunicatively coupled with web server 250 and/or content server 251during rendering and presentation of the content disposed on mediastorage device 999.

Additionally, media content 2001-M having a first encryption appliedthereto, e.g., encryptions 1351-N, can each be subject to a secondencryption, e.g., encryptions 2351-P, respectively, prior to disposal ofmedia content 2001-N on media storage device 999. In one embodiment, asecond decryption key to decrypt encryptions 2351-P may be stored in aserver, (e.g., web server 250 and/or content server 251 of FIGS. 2, 4,10, and 14). In one embodiment, file system filter driver 1220 canutilize decrypter 1221 and the second decryption key stored on webserver 250 and/or content server 251 to decrypt encryptions 2351-Pduring the reading of the content on media storage device 999 by mediastorage device drive 1112. It is noted that file system filter driver1220 can be communicatively coupled with web server 250 and/or contentserver 251 during rendering and presentation.

In one embodiment, encryptions 1351-N can be less computationallyintensive encryptions when compared to encryptions 2351-P.Alternatively, in one embodiment, encryptions 1351-N can be morecomputationally intensive when compared to than encryptions 2351-P.

There are many available encryption methods that can be implemented asencryptions 1351-N and/or encryptions 2351-P. Examples of encryptionsthat may be implemented for encryptions 1351-N and/or 2351-P caninclude, but are not limited to, triple DES (data encryption standard),AES (advanced encryption standard), Blowfish, and numerous others. Inone embodiment, encryptions 1351-N and/or 2351-P can each be comprisedof a series and/or a mixture of encryptions. A differing encryption,e.g., a plurality of randomly generated encryptions, can be implementedfor each instance of media on a media storage device, rather than usingone format. In one embodiment, numerous variations of Blowfish areutilized to provide the desired encryptions.

It is noted that when the media (e.g., 2001) of media storage device 999is encrypted utilizing multiple different encryptions (e.g., 1351 and2351), the media is more secure against those with dishonest and/orunlawful interests. For example, a person/hacker may attempt to gainaccess to the content by breaking the second encryption (e.g., 2351)applied to a media content (e.g., 2001). However, if they aresuccessful, the remaining encryption, (e.g., 1351) remains unbroken byvirtue of the differing encryptions. Therefore, the person/hacker wouldhave to perform the entire encryption breaking process again to accessmedia content 2001 on media storage device 999. Thus, after spendingnon-trivial amounts of time breaking two differing encryptions appliedto an instance of media (e.g., 2001) the remaining content on mediastorage device 999 can still be encrypted, each with it own differingmultiple encryptions.

FIG. 14 is a block diagram of a communicative environment 1400 forcontrolling presentation of media content disposed on a media storagedevice. Included in communicative environment 1400 is a media storagedevice drive 1112 coupled with a client computer system 210 via adata/address bus 110. Client computer system 210 is coupled with webserver 250 and/or content server 251 via Internet 201. A media storagedevice 999, upon which a usage compliance mechanism 1200 may bedisposed, is received by in media storage device drive 1112. Autorunprotocol component 910 detects the reception and automatically invokesinstallation of CCM 300, file system filter driver 1220, and securemedia player 1210 from media storage device 999 into client computersystem 210. Subsequent to installation, UCM 1200 initiates a dynamicupdate with web server 250 and/or content server 251, via Internet 201,as described herein with reference to FIGS. 3, 4, and 7A-7C, therebycontrolling the integrity of the software. Additionally, by conferringwith servers 250 and/or 251 via Internet 201 online, the UCM 1200software version on media storage device 999 and installed on clientcomputer system 210 can be updated when circumventions occur and keptcurrent from platform to platform.

Advantageously, the monitoring mechanism of agent program 304 enablesconstant morphing of the version of CCM 300 disposed on media storagedevice 999 by communicating with server 250 and/or 251 and utilizing thedynamic update capabilities of global network 800 to readily update thatwhich has been installed on client computer system 210, via mediastorage device 999.

In one embodiment, the installation is performed clandestine withrespect to the recipient of media storage device 999 and is initiated byinserting media storage device 999 into an appropriate media storagedevice drive, (e.g. a magnetic/optical disk drive or alternative devicedrive) coupled with client system 210. Portions of UCM 1200 determine ifthe recipient is registered with web server 250 and/or content server251. If the recipient is not registered with servers 250 and/or 251, asdescribed herein with reference to FIGS. 4, 7A-7C, and 8, portions ofUCM 1200 initiates an installation process as described herein withreference to FIGS. 3, 4, 7A-7C, and 11.

If computer system 210 is registered with servers 250 and/or 251, UCM1200 can initiate an update process with web server 250 and/or contentserver 251 to readily include updates that have been invoked subsequentto distribution of media storage device 999. By virtue of the dynamicupdate capabilities of UCM 300, regardless of the version of CCM 300 onmedia storage device 999, UCM 1200 provides compliance with copyrightrestrictions and/or licensing agreements applicable to the media contenton media storage device 999, (e.g., media content 2001-M).Advantageously, enabling dynamic adaptability of UCM 1200 provides forcontinued interoperability with new and updated operating systems,advancements in electronic technology, communication technologies andprotocols, and the like, ensuring the effectiveness of UCM 1200 into thefuture.

In another embodiment, if the user is a registered user with globaldelivery system 800, UCM 1200 can detect which version is most current.Accordingly, when the version existing on client system 210 is morecurrent that the version (for install) on media storage device 999, UCM1200 can bypass the install process and present the contents containedon media storage device 999 to the user for them to experience.

Further advantageous, this technology is backward compatible with mediastorage device drives manufactured subsequent to 1982. Additionally, UCM1200 is compatible with media storage devices having a copyrightindicator bit disposed thereon. The copyright indicator bit has beenincluded on all CDs released since 1982.

In the present embodiment of FIG. 14, each instance of media isencrypted on media storage device 999, as described herein withreference to FIG. 13. However, most home players and/or stand alonemedia playing devices rarely include a decryption mechanism. As such, toexperience the music on a home machine, the music is conventionally notencrypted. Accordingly, media storage device 999, in its presentembodiment, may not be operable on a home and/or stand alone mediaplaying device.

In one embodiment, UCM 1200 can invoke its own proprietary player,(e.g., secure media player 1210), as described with reference to custommedia device 310 of FIG. 3, thus enabling increased control of copyrightrestrictions and/or licensing agreements applicable to the mediacontent. By invoking a secure media player 1210, UCM 1200 enables userexperience of media content while providing protection againstunauthorized presentation or reproduction of the media disposed on mediastorage device 999.

Still referring to FIG. 14, in one embodiment, the media content, (e.g.,media content 2001-M), and UCM 1200 disposed on a media storage device999 are encrypted, with the exception of autorun protocol 910, asdescribed above. In one embodiment of the present invention, UCM 1200 isencrypted differently than media content 2001-M, thereby preventing thecracking of one encryption from being utilized on another encryption.This implementation is particularly advantageous for demonstration(demo) versions of media files, beta test versions, and the like thatmay be disposed on media storage device 999. It is noted that thepresent embodiment is operable in an online environment, meaning thatclient computer system 210 can be communicatively coupled with webserver 250 and/or content server 251 to enable a user experience of thecontent on a demo version of media storage device 999. In thisimplementation, UCM 1200 allows for specific plays for specific users,which can be controlled via a network, (e.g., network 1400), and server250 and/or 251.

In the present embodiment, UCM 1200 can be implemented for demonstrationand/or pre-release protection of content disposed on a media storagedevice 999. However, content disposed on media storage device 999 canalso be commercially released content, (e.g., audio, video, software,and the like). In this embodiment, sophisticated encryption technology,(e.g., Blowfish), is utilized to encrypt media content 2001-M on mediastorage device 999 with an associated decrypter key located on webserver 250 and/or content server 251. In one embodiment, a plurality ofencryptions are applied to media content 2001-M and a plurality ofdecrypter keys are stored on web server 250 and/or content server 251.Decryption can be performed using an associated decryption key inconjunction with a secure media player 1210 and file system filterdriver 1220 installed on computer system 210 via media storage device999.

Still with reference to FIG. 14, the content (e.g., media content2001-M) of media storage device 999, is encrypted using various levelsof encryption to provide protection levels commensurate with copyrightholders desires and required protection. For example, media storagedevice 999 is delivered to a user or critic for the purposes of review.The user inserts media storage device 999 into the appropriate storagedevice reader or connector coupled with the recipient's computer, andautorun protocol 910 initiates UCM 1200 install of CCM 300, file systemfilter driver 1220, secure media player 1210 on client system 210 in amanner clandestine to the user. Once installed, UCM 1200 initiates acommunication session with web server 250/content server 251, wherecontent server 251 can provide authorization for the user to experiencethe media on media storage device 999.

Accordingly, if the user, to whom demo media storage device 999 had beenreleased, had demo media storage device 999 stolen, or if the userallowed alternative parties to try to experience the content of mediastorage device 999, the unauthorized party would have to try to crackthe encryption keys and the encryption of the actual content of mediastorage device 999, consuming non-trivial amounts of time.

Thus, UCM 1200 is able to control which recipients receive authorizationto experience the media content on media storage device 999, how manytimes the recipient may experience the media, and UCM 1200 may alsodefine a period of time beyond which the media content may no longer beaccessible. This may enable copyright holders to release the mediacontent on an authorized media storage device, (e.g., 999), prior topirated copies flooding the market.

Still referring to FIG. 14, accordingly, a media storage device 999 maybe configured such that a first user may get a copy, a second user mayget a copy, and if it is known that the second user will share the demowith a third and a fourth user, then the known users would be enabled toexperience the media. Advantageously, by virtue of defining which userscan access and experience the media, any unauthorized sharing of themedia by one of the authorized users can be readily detected, andfurther sharing or experiencing of the media may be halted.Additionally, since the authorized user shared the media in anunauthorized manner, in a worse case scenario, criminal charges could befiled against that user.

It is noted that by including placing UCM 1200 on a media storagedevice, (e.g., 999), so as to enable installation of CCM 300 on clientsystem 210 is one manner in which CCM 300 can be installed on clientsystem 210. An alternative manner in which CCM 300 can be installed onclient computer system 210 is through “cross-pollination.” For example,webcasters broadcast the media file to the user. The media file has aCCM 300 coupled with the media file, and upon downloading the media fileonto client computer system 210, embodiments of the present inventionenable the installation of CCM 300 onto client computer system 210. Inanother manner, CCM 300 is incorporated into and becomes part of anoperating system operational on client system 210. Alternatively, lawsare passed that mandate the inclusion of CCM 300 on each client computersystem 210.

FIG. 15 is an exemplary logic/bit path block diagram 1500 of a clientcomputer system, (e.g., 210), configured with a usage compliancemechanism (e.g., 1200) for controlling presentation of content on amedia storage device (e.g., 999), in accordance with one embodiment ofthe present invention. It is noted that usage compliance mechanism 1200of FIG. 15 is analogous to usage compliance mechanism 1200 of FIG. 12.Therefore, CCM 300 of usage compliance mechanism 1200 is analogous to acopyright compliance mechanism 300 coupled with and installed on aclient computer system, (e.g., 210), as described herein with referenceto FIGS. 3, 4, 5A-5D, 6A, 7A-7C, 8, 9, 10, 11 14, 15, and 16.

Diagram 1500 includes a media storage device drive (e.g., 1112) coupledwith a media storage device file system driver 1114 via line 1571. Mediastorage device drive file system driver 1114 enables an operatingsystem, (e.g., Windows by Microsoft, Apple, Linux, etc.), on a clientcomputer system, (e.g., 210), to recognize and control the media storagedevice drive 1112. Coupled to media storage device drive file systemdriver 1114 is file system filter driver 1220, via line 1572. Coupled tofile system filter driver 1220 is a secure media player 1210 via line1573. Coupled with secure media player 1210 are an operating systemmedia subsystem 503 via line 1577 and a media hardware output device1370 via line 1574. UCM 1200 is coupled with operating system mediasubsystem 503 via line 1576.

Media storage device drive 1112 of FIG. 15 is analogous to media storagedevice drive 1112 of FIGS. 11 and 14. Media storage device drive 1112 isconfigured to receive a media storage device 999. In one embodiment,drive 1112 may be a CD drive and media storage device 999 would be a CD.In another embodiment, drive 1112 may be a DVD drive and accordingly,media storage device 999 would be a DVD, and so on. Therefore, mediastorage device drive 1112 can, when so configured, receive any mediastorage device 999 upon which data or content may be disposed.

File system filter driver 1220 can be an upper level and/or lower levelfilter for individual bus devices, (e.g., media storage device drive1112), within client computer system 210, and is analogous to filesystem filter driver 1220 of FIG. 12. File system filter driver 1220 isable to hook onto access of media storage device drive 1112, (e.g., a CDdrive) and intercept data reads associated with accessing the content,(e.g., media content 2001-M), of media storage device 999. File systemfilter driver 1220 is also enabled, via decrypter 1221 and a decrypterkey on servers 250 and/or 251, to provide dynamic decryption ofencrypted media content on media storage device 999 as the content isaccessed and read by media storage device drive 1112.

By virtue of file system filter driver 1220 operating at a file systemlevel instead of operating at a device drive class level, (e.g., a CDclass level), it is able to recognize which files are being accessedfrom media storage device 999 for a particular operation.Advantageously, this obviates the need for a file system to beimplemented within a driver for determining whether data that is beingread needs decrypting.

Still referring to FIG. 15, secure media player 1210 is analogous tosecure media player 1210 of FIG. 11. Secure media player 1210 can, inone embodiment, be a custom media device 310 emulated by a custom mediadevice driver 307, as described herein with reference to FIG. 3. Inanother embodiment, secure media player 1210 can be a proprietary playerconfigured for utilization with demonstration and/or pre-release contentdisposed, (e.g., 2001-M), on a media storage device, (e.g., 999). Otherauthorized media players may also be used to present media content of amedia storage device 999, provided the other media players can complywith usage restrictions and/or licensing agreements applicable to themedia content and provided by secure media player 1210.

Media hardware output device 1370 is an appropriate output device forthe media content of media storage device 999. If media content 2001-Mare audio tracks or songs, then output device 1370 is an audio or soundcard for outputting music via speakers. Alternatively, if media content2001-M are video tracks, movies, literary works, software programs,etc., then output device 1370 is a graphics card for outputting movies,text, and the like via a display device, (e.g., 105 of FIG. 1).

Continuing with FIG. 15, media storage device 999 is received by mediastorage device drive 1112. Autorun protocol 910 initiates a process todetermine the presence of a usage compliance mechanism 1200 and a securemedia player, (e.g., 1210), operable on computer system 210. If eitherand/or both usage compliance mechanism 1200 and secure media player 1210are not present on computer system 210, autorun protocol 910 initiatesinstallation of the components, as described herein with reference toFIGS. 3, 4, 5A-5D, 6, 7A-7C, and 8-16. If UCM 1200 and secure mediaplayer 1210 are both present, autorun 910 bypasses the installationthereof. Media storage device file system driver 1114 accesses thecontent, (e.g., 2001-M), on media storage device 999 and reads the data.

File system filter driver 1220 intercepts the read operation beingperformed by driver 1114 and dynamically decrypts a second encryption,(e.g., 2351-P), applied to media content 2001-M via decrypter 1221 and asecond decryption key stored on and retrieved from servers 250 and/or251. In one embodiment, if file system filter driver 1220 is notcommunicatively coupled with server 250 and/or 251, thereby enablingretrieval of the second decryption key, presentation of the content ofmedia storage device 999 is not permitted.

Continuing with FIG. 15, subsequent to the second encryptions 2351-Pbeing decrypted, media content 2001-M, which is still encrypted with afirst encryption, (e.g., 1351-N, respectively), is output to securemedia player 1210 via line 1573. Secure media player 1210 in conjunctionwith UCM 1200 communicates with server 250 and/or 251 and determines ifcomputer system 210 and the user thereof, are authorized to experiencemedia content 2001-M. If system 210 and the user thereof are authorizedto experience media content 2001-M, secure media player 1210 commencesto render the media content for presentation via media hardware outputdevice 1370.

Concurrent with rendering media content 2001, secure media player 1210can, in one embodiment, communicate with server 250 and/or 251 andretrieve the decryption key associated with each encryption, (e.g.,1351-N), and with decrypter 1211 of FIG. 12, in order to dynamicallydecrypt each instance of media, (e.g., 2001-M), as the content is beingrendered and output via line 1574 to media hardware output device 1370.

Because rendered content is vulnerable to capture and/or imaging, andthus becoming subject to ripping, burning, copying, and the like, securemedia player 1210 can watermark, (e.g., via watermarker 1212), theoutgoing data stream that is output to media hardware output device 1370via line 1574. In one embodiment, utilizing watermarker 1212, theoutgoing data stream is watermarked concurrent with the renderingperformed by secure media player 1210. Further, secure media player 1210can attach a unique identifier, (e.g., 1380), with each rendered mediacontent (e.g., 2001-M). In one embodiment, the unique identifier 1380 isa serial number that is attached to each media content, (e.g., 2001-M),as it is being rendered and output to media hardware output device 1370.In this manner, if the rendered content being output is somehowcaptured, imaged, etc., by virtue of the association of uniqueidentifier 1380, (e.g., serial number), with media storage device 999and the media content disposed thereon, (e.g., content 2001-M), andcomputer system 210 with which the recipient of media storage device 999is associated, unauthorized presentation and reproduction of the mediacontent is prevented.

FIG. 16 is a flowchart 1600 of computer implemented steps performed inaccordance with one embodiment of the present invention for controllingpresentation of media content disposed on a media storage device.Flowchart 1600 includes processes of the present invention, which, insome embodiments, are carried out by processors and electricalcomponents under control of computer readable and computer executableinstructions. The computer readable and computer executable instructionsreside, for example, in data storage features such as computer usablevolatile memory 104 and/or computer usable non-volatile memory 103 ofFIG. 1. However, the computer readable and computer executableinstructions may reside in any type of computer readable medium.Although specific steps are disclosed in flowchart 1600, such steps areexemplary. That is, the present embodiment is well suited to performingvarious other steps or variations of the steps recited in FIG. 16.Within the present embodiment, it should be appreciated that the stepsof flowchart 1600 may be performed by software, by firmware, by hardwareor by any combination thereof.

It is noted that flowchart 1600 is described in conjunction with FIGS.2, 3, 4, 5A-5D, 6, 7A-7C, and 8-15 to more fully describe the operationof the present embodiment. At operation 1610, an autorun mechanism,(e.g., autorun protocol 910), disposed on a media storage device (e.g.,999), is activated in response to a computer system, (e.g., 210),receiving the media storage device in an appropriate device drive,(e.g., media storage device drive 1112).

At operation 1612 of FIG. 16, a monitoring program disposed on mediastorage device 999 determines if a usage compliance mechanism, (e.g.,UCM 1200), is installed on the computer system (e.g., 210) whichreceived media storage device 999. In one embodiment, agent programs 304may perform the determination at operation 1612. However, in anotherembodiment, combinations of components of a CCM 300, as described hereinwith reference to FIG. 3, 4, 7A-7C may be utilized to perform thedetermination at operation 1612. If a usage compliance mechanism is notpresent on computer system 210 at operation 1612, process 1600 proceedsto operation 1611. Alternatively, if a usage compliance mechanism ispresent on computer system 210 at operation 1612, the process 1600proceeds to operation 1614.

At operation 1611, a usage compliance mechanism can be installed oncomputer system 210. It is noted that the installation of the usagecompliance mechanism on computer system 210 at operation 1611 may beperformed in a wide variety of ways in accordance with the presentembodiment. For example, the installation can be implemented atoperation 1611 as described herein with reference to FIGS. 3, 4, 5A-5D,6, 7A-7C, and 8-15, but is not limited to such.

At operation 1614, a monitoring mechanism (e.g., of UCM 1200) disposedon media storage device 999 determines if a secure media player, (e.g.,1210) is present and operable on computer system 210. In one embodiment,agent program 304 of CCM 300 of FIG. 3 can perform the determination atoperation 1611. If a secure media player, (e.g., 1210) is not presentand operable on computer system 210 at operation 1614, the presentmethod proceeds to operation 1611. Alternatively, if a secure mediaplayer (e.g., 1210) is present and operable on computer system 210 atoperation 1614, the present method proceeds to operation 1616.

At operation 1611 of FIG. 16, a secure media player (e.g., 1210) can beinstalled on computer system 210. It is noted that the installation ofthe secure media player on computer system 210 at operation 1611 may beperformed in diverse ways in accordance with the present embodiment. Forexample, the installation can be implemented at operation 1611 asdescribed herein with reference to FIGS. 3, 4, 5A-5D, 6, 7A-7C, and 8-15but is not limited to such.

At operation 1613, a determination is made as to whether theinstallation (e.g., of a usage compliance mechanism and/or a securemedia player) at operation 1611 was successful. If so, process 1600proceeds to operation 1616. However, if it was determined at operation1613 that the installation at operation 1611 was not successful, process1600 proceeds to operation 1616.

At operation 1616, a determination is made as to whether computer system210 and the user thereof are authorized to experience media content(e.g., 2001-M) of media storage device 999. It is noted that thedetermination at operation 1616 may be performed in a wide variety ofways in accordance with the present embodiment. For example, the usagecompliance mechanism (e.g., 1200) can communicate with servers 250and/or 251 in networks 200, 400, 1000 and/or 1400 to determine whethercomputer system 210 and its user are authorized to experience mediacontent (e.g., 2001-M) on media storage device 999, as described hereinwith reference to FIGS. 3, 4, operations 704-708 of FIG. 7A, and FIGS.8-15, but is not limited to such. If computer system 210 and its userare not authorized to experience the content on media storage device 999at operation 1616, process 1600 proceeds to operation 1615.Alternatively, if computer system 210 and its user are authorized toexperience the content on media storage device 999 at operation 1616,process 1600 proceeds to operation 1618.

At operation 1618 of FIG. 16, a determination is made (e.g., by UCM1200) as to whether secure media player 1210, usage compliance mechanism1200 and computer system 210 are all communicatively coupled with anetwork (e.g., 200, 400, 800, 1000, and/or 1400) in accordance with thepresent embodiment. If one or more of the conditions are not met atoperation 1618, the present method proceeds to operation 1615.Alternatively, if secure media player 1210, usage compliance mechanism1200 and computer system 210 are all communicatively coupled with thenetwork (e.g., 200, 400, 800, 1000, and/or 1400) at operation 1618, thepresent method proceeds to operation 1620.

At operation 1615, the presentation of content (e.g., 2001-M) of mediastorage device 999 to the user of computer system 210 is prevented.Alternatively, computer system 210 and the user thereof may communicatewith the network (e.g., 200, 400, 1000, and/or 1400) and attempt toestablish credentials and/or to re-establish a communicative couplingwith the network that would allow presentation of the content, asdescribed herein with reference to FIG. 3, 4, and steps 704-708 of FIG.7A.

At operation 1622, the session is ended.

At operation 1620 of FIG. 16, media content (e.g., 2001-M) of mediastorage device 999 can be presented to the user of computer system 210.It is noted that operation 1620 can be implemented in a wide variety ofways in accordance with the present embodiment. For example, the mediacontent (e.g., 2001-M) on media storage device 999 can be read by mediastorage device drive 1112. File system filter driver 1220 can interceptsthe read operation being performed by media storage device file systemdriver 1114 and dynamically decrypts a second encryption (e.g., 2351-P)applied to media content 2001-M via decrypter 1221 and a seconddecryption key stored on and retrieved from servers 250 and/or 251.Within an embodiment, if file system filter driver 1220 is notcommunicatively coupled with server 250 and/or 251, enabling retrievalof the second decryption key, presentation of the content on a mediastorage device 999 is not permitted.

Continuing with an exemplary implementation of operation 1620,subsequent to a second encryption (e.g., 2351-P) being decrypted, mediacontent 2001-M, which is still encrypted with a first encryption, (e.g.,1351-N, respectively), is output to secure media player 1210. In oneembodiment, secure media player 1210, in conjunction with UCM 1200,communicates with server 250 and/or 251 and commences to render themedia content for presentation via a media hardware output device,(e.g., 1370).

It is noted that concurrent with rendering media content, (e.g.,2001-M), secure media player 1210, can, in one embodiment, communicatewith server 250 and/or 251 and retrieve the decryption key associatedwith each encryption, (e.g., 1351-N), and with decrypter 1211 of FIG.12, dynamically decrypt each instance of media, (e.g., 2001-M) as thecontent is being rendered and output the rendered content to mediahardware output device 1370.

Since rendered content is vulnerable to capture and/or imaging, and thusbecoming subject to ripping, burning, copying, and the like, securemedia player 1210 can watermark, (e.g., via watermarker 1212), theoutgoing data stream that is output to media hardware output device1370. In one embodiment, the outgoing data stream is watermarkedconcurrent with the rendering performed by secure media player 1210.Further, secure media player 1210 attaches a unique identifier (e.g.,1380) with each rendered media content 2001-M. In one embodiment, aunique identifier 1380 (e.g., a serial number) is attached to each mediacontent (e.g., 2001-M), as it is being rendered and output to mediahardware output device 1370. In this manner, if the rendered contentbeing output is somehow captured, imaged, etc., by virtue of theassociation of unique identifier 1380 with media storage device 999 andthe media content (e.g., 2001-M) disposed thereon and the computersystem 210 with which the recipient of media storage device 999 isassociated, unauthorized presentation and reproduction of the mediacontent is prevented.

In another implementation, embodiments of the present invention can beutilized in a distributed network topology to control media sharingamong computer system within the network. Some of the distributednetwork topologies in which embodiments of the present invention can beutilized are, but is not limited to, a centralized, a ring, ahierarchical, and a decentralized distributed topology. A decentralizeddistributed network topology is commonly referred to as a peer-to-peer(P2P) network. In a P2P network, each computer system/node in thenetwork is able to communicate with any other computer system/nodewithin the network. A computer system in a P2P network can request datafrom the network as well as provide data to the network. Thus, acomputer system can be both a requesting computer system (requestingnode) and a source computer system (source node) within a P2P network.Additionally, there may be a host server or a plurality of host serverspresent in the network that may be utilized alone or in combination witheach other (e.g. as an administrative node, supernode, etc.) to provideadministrative functionalities to the computer systems therewithin andfor providing content to the P2P network.

It is known that many implementations of a distributed network topology,(e.g., a decentralized topology), are not configured to adequatelycontrol and/or monitor the exchanging or trading of media among computersystems in the P2P network. Embodiments of the present invention providea novel and inventive solution to this problem.

FIG. 17 is a block diagram of a network environment 1700 for sharingmedia content between nodes (e.g., computer systems) communicativelycoupled therewith, in accordance with one embodiment of the presentinvention. Network 1700 includes a client node 1705, a source node 1715and an administrative node 1770 which are communicatively coupled viacommunication link 1710. Communication link 1710 may be a wireline,wireless, or combination of wireline and wireless technologies andcommunication protocols that facilitate interaction between computersystems. Additionally, in the present embodiment, nodes 1705, 1715, and1770 may each implemented in a similar manner to that described hereinwith reference to FIG. 1. Further, network environment 1700 may beimplemented in a manner similar to that described herein with referenceto network 200 of FIG. 2 and network 800 of FIG. 8.

In one embodiment, client node 1705 may be implemented in a mannersimilar to a client computer system 210 as described herein withreference to FIGS. 2, 4-8, 10, 11, 14, and 15. Source node 1715 may, inone embodiment, be a client computer system 1705 that makes available tonetwork 1700 media content that may be stored therewithin. In anotherembodiment, source node 1705 may be a media distribution point (MDP) asdescribed herein with reference to FIG. 8, configured to make availableto network 1700 media content that may be stored therewithin. By virtueof the functionality inherent to a P2P network, source node 1715 canfunction as a client node while client node 1705 can function as asource node.

Still referring to FIG. 17, administrative node 1770 may, in oneembodiment, be implemented in a manner similar to a web server 250and/or content server 251, as described herein with reference to FIGS. 2and 4. As such, administrative node 1770 may also be coupled to adatabase, (e.g., database 451 and/or 451 of FIG. 4). Accordingly,administrative node 1770 can, in one embodiment, be configured toprovide management functionalities to a network, (e.g., network 1700 ornetwork 800 of FIG. 8). Types of management functionalities that can beprovided by administrative node 1770 can include, but is not limited to,network management, user management, encryption and decryption keymanagement, authorization management, media management, transactionmanagement, player application management, and cache management.Administrative node 1770 can also be implemented as a source node 1715and/or as a media delivery point as described herein with reference toFIG. 8.

Network management can include, but is not limited to, determining theroute through which an instance of media is transferred to anothercomputer system in network 1700. For example, and referring to FIG. 8,an instance of media is located in a plurality of locations withinnetwork 800, e.g., media delivery points 808 (San Jose), 816 (Tokyo),and 812 (New York City). Client node 1705 located in Washington D.C.requests that particular instance of media content. Administrative node1770 is able to determine, for this example, that the least amount ofnetwork resources needed to transfer the media content to requestingclient node 1705 would be transferring the instance of media contentfrom media delivery point 812 (New York City).

It is anticipated that many instances of a particular instance of mediamay be disposed throughout the network, (e.g., 1700), in which there maybe varying degrees of quality among the instances media content.Further, it is known that differing source nodes (e.g., 1715) can havevarying rates of transfer. For example, a source node 1715 may becoupled to network 1700 via a digital subscriber line (DSL), whereasanother source node 1715 may be coupled to network 1700 via a 56K modem,which is substantially slower than a DSL connection. Additionally,transfer routes that would go through a network connection that may beexperiencing downtime or technical difficulties can be rerouted.Advantageously, administrative node 1770 can incorporate quality ofmedia content, connection health, and/or delivery speed information intoits determination from which source node 1715 the instance of media isto be delivered.

Still referring to FIG. 17, user management, in one embodiment, caninclude, but is not limited to, maintaining and verifying current userinformation such as user name, password, billing address, valid creditcard number, valid online payment or alternative electronic paymentservice, MAC (media access control) address, etc., as described hereinwith reference to FIGS. 3 and 4, and steps 704-710 of FIGS. 7A-7C.

In one embodiment, encryption and decryption key management includes,but is not limited to, storing an encryption key associated with aclient computer system for use by the client computer system to encryptmedia content thereon into an encryption local to that client computersystem, managing a plurality of intermediate encryption and decryptionkeys for utilization with media content that is being transmitted to aclient computer system, etc.

In one embodiment, encryption and decryption key management includes,but is not limited to, storing an encryption key associated with aclient node (e.g., 1705) for use by the client node to encrypt mediacontent thereon into an encryption local to that client node, managing aplurality of intermediate encryption and decryption keys for utilizationwith media content that is being transmitted to a client node, etc.

In one embodiment, authorization management may include verifying that aclient node 1705 is authorized to be connected to network 1700, thusbeing associated with the network. Alternatively, authorizationmanagement may also include, but is not limited to, authorizing sharingof an instance of media with network 1700 that does comply withcopyright restrictions and/or licensing agreements applicable to theparticular instance of media. Furthermore, authorization management mayinclude, but is not limited to, prohibiting sharing of an instance ofmedia with network 1700 that does not comply with copyright restrictionsand/or licensing agreements applicable to the particular instance ofmedia.

Still referring to FIG. 17, media management can include, but is notlimited to, storing a list of available instances of media content andits associated location within network 1700, storing information relatedto each instance of media, (e.g., title, artist, genre, length/durationof media content, bit pattern information related to a particularinstance of media for identification, storing information regardingroyalty fees (where applicable) that may be assessed to an instance ofmedia content each time it is transmitted within the network), storinginformation to enable expiring the media content on a computer systemwhen the computer system is no longer authorized to access and/or is nolonger associated with network 1700, and the like.

Additionally, media management can also include utilizing an Ethernetfilter and other mechanisms to obtain information related to transmittedand/or received instances of media, instances of media that haverecently entered the network, and the like. In one embodiment, anEthernet filter may be coupled to a network interface device (e.g., 104)coupled to the computer system receiving the instance of media content.It is noted that the network interface may include, but is not limitedto, a modem, a NIC (network interface card), a wireless receiver, etc.Information obtained by an Ethernet filter can be used in identifying aparticular instance of media, determining appropriate royalty fees, etc.

In one embodiment, transaction management can include generating atransaction for each successful transfer of media content from one node(e.g., source 1715) to another node (e.g., client 1705) in the network,e.g., from source computer system 1715 to client computer system 1705 inthe network (e.g., 1700). In one embodiment, the receiving client node1705 acknowledges successful receipt of the media content andaccordingly, administrative node 1770 generates a transaction applicableto the receiving client node 1705 and which is associated with thatparticular instance of media. Since different instances of media contentmay have differing usage and/or royalty fees associated therewith,embodiments of the present invention can provide the mechanisms toaccount for each transfer such as generating a transaction for eachtransfer, generating a payment from the recipient of the instance ofmedia, and/or delivering an appropriate remuneration to the mediacontent copyright holder.

Advantageously, a royalty transaction can also be applied to acopyrighted instance of media where no royalty payment was previouslypossible. For example, assume that a bootleg copy of an artist's liveperformance has been freely available for years. This bootleg copy mayhave been made from a portable recorder brought into a live performanceand was used to record the performance. In this example, a personacquires an analog bootleg copy and converts it to a digital format oracquires a digital format of the bootleg copy. The digital copy is thenavailed to network 1700 for sharing among the nodes coupled therewith.It is noted that when an instance of media enters network 1700, itbecomes protected as described herein with reference to FIGS. 3, 4-9,11, 12, and 15.

Accordingly, when a client node 1705 successfully receives the digitalcopy, a transaction is generated, thus invoking a royalty payment whenno such royalty payment was previously possible. Advantageously, thiscan provide a means to distribute appropriate remuneration to copyrightholders and licensees that would otherwise receive no payment.

Continuing, when an instance of media can be freely distributed, atransaction is still generated. This advantageously provides a record ofthe numbers of requests for a particular instance of media, the locationfrom where those requests originated, and the like, thereby providingdata which can be utilized in marketing studies and implementingmarketing strategies, etc.

It is particularly noted that in an alternative implementation,embodiments of the present invention can be readily configured toprovide a mechanism that can generate a sales/use tax transactionrelated to transfer of a instance of media. Embodiments of the presentinvention can be readily configured to calculate appropriate sales/usetax amounts relative to the location of the receiving client computersystem. Advantageously, this would enable municipalities, counties,states, and other governmental agencies to increase revenue, thuspossibly realizing a reduction in a deficit associated with agovernment. It is anticipated that generating sales/use tax transactionscould provide from tens to hundreds of millions of dollars in previouslyuntapped revenue to those governmental agencies.

Still referring to FIG. 17, player management, in one embodiment, caninclude, but is not limited to, maintaining secure player applicationintegrity, adding additional player applications to a list of approvedplayer applications, removing player applications that do not meet usagerestriction requirements applicable to a media file, modification of asecure player application to improve its functionality, modification tocounteract nefarious hacking attempts, disabling the secure playerapplication when the computer system on which it is operable is nolonger authorized to participate in or is associated with network 1700,etc.

Cache management, in one embodiment, can include, but is not limited to,maintaining protected media container file integrity, modificationthereof to improve functionality or to counteract detected nefariousactivities, disabling the protected media container file when thecomputer system upon which the protected media container file isdisposed is not authorized to access and/or is no longer associated withnetwork 1700.

In the present embodiment, client node 1705 and source node 1715 eachhave an instance of a usage compliance mechanism (UCM) 1800 coupledtherewith. In the present embodiment, UCM 1800 of FIG. 17 and asdescribed with detail in FIG. 18 is similar to a copyright compliancemechanism 300 and/or a usage compliance mechanism 900 and/or 1200, asdescribed herein with reference to FIGS. 3, 4, 5A-5D, 6A, and/or 9, 11,12, and 15, respectively.

FIG. 18 is a block diagram of components in a usage compliance mechanism(UCM) 1800 that is configured to be installed and operable on a clientnode (e.g., 1705) and/or a source node (e.g., 1715) in accordance withan embodiment of the present invention. UCM 1800 includes a copyrightcompliance mechanism (e.g., 300) that can be analogous to a copyrightcompliance mechanism 300 as described herein with reference to FIGS. 3,4, 5A-5D and 6A. It is noted that UCM 1800 also includes those featuresand components as provided in a UCM 900 and a UCM 1200 as describedherein with reference to FIGS. 9, 11, 12, and 15, respectively.

UCM 1800 further includes a secure player application 1810, a clientcommunication application 1820, and a media storage container creator1830. Media storage container creator 1830 is configured to allocate aportion of a memory unit coupled to the computer system in which UCM1800 is installed, (e.g., 102 and/or 103) coupled to the computer system(e.g., 100) into which UCM 1800 is installed. Media storage containercreator 1830 utilizes the allocated portion of a memory unit and createsa protected media container file (e.g., a custom file system) into whichreceived and/or availed instances of media, (e.g., audio files, videofiles, multimedia files, documents, software, and the like) are stored.It is noted that in one embodiment, media content that is stored in aprotected media container file (not shown) is, in addition to otherencryptions applicable to the instance of media, encrypted local to thecomputer system on which the protected media file container is disposed.In an example, an instance of media is stored on both client node 1705and source node 1715 of FIG. 17. Accordingly, media content is uniquelyencrypted local to node 1705 and is uniquely encrypted local to node1715. Additionally, in the context of the present invention, the termavailed and/or availing refers to making available to a network, (e.g.,1700), an instance of media that may be stored in a protected mediacontainer file.

Still referring to FIG. 18, UCM 1800 also includes, in one embodiment, aclient communication application 1820. Client communication applicationis a custom client communication application configured to providecommunication functionality between the nodes in a decentralizeddistributed network, (e.g., 1700). Alternatively, client communicationapplication 1820 is also well suited to be implemented in nearly anynetwork, including, but not limited to, network 1700. Clientcommunication application 1820 can be a well known and readily availablecommunication application and which may be written in a commonlyutilized programming language including, but not limited to, C, C++,Java, Fortran, etc.

In one embodiment, client communication application 1820 is configuredto decrypt media content from an encryption local to a computer systemon which application 1820 is operable. Client communication application1820 can also be configured to encrypt media content into anintermediate encryption for transferring the media content to anothercomputer system communicatively coupled with a network, (e.g., 1700).Application 1820 is additionally configured to decrypt media contentthat is received in an intermediate encryption from a computer systemcoupled with network 1700. Client communication application 1820 isfurther configured to encrypt the media content into an encryption localto the computer system on which application 1820 is operable.

In one embodiment, client communication application 1820 can utilize anintermediate encryption key provided by an administrative node (e.g.,1770) to encrypt the media content into the intermediate encryption fortransfer. Application 1820 can also utilize an intermediate decryptionkey, also provided by administrative node 1770, to decrypt media contentthat is received in an intermediate encryption from a computer systemcoupled with network 1700.

In one embodiment, client communication application 1820 can transmit anindicator or an acknowledge signal indicating that the media contentdelivered from another computer system in network 1700 was successfullyreceived. In one embodiment, an acknowledge signal received byadministrative node 1770 can generate a transaction applicable to thecomputer system receiving the media content and which is associated withthe media content that was received.

Still referring to FIG. 18, UCM 1800 further includes a secure playerapplication 1810 that can be configured to access contents of aprotected media container file, (e.g., an instance of media) and providepresentation of the media content to the computer system on which themedia content is stored. Secure player application 1810 can be furtherconfigured to utilize its access to the protected media container fileand make available to the network the contents thereof. In oneembodiment, secure player application 1810 can present the media contentto the computer system on which it is operable while the computer systemis offline, (e.g., not coupled with network 1700 but still associatedtherewith).

Secure player application 1810 can be media type specific, such as asecure audio player application for audio files, a secure video playerapplication for video files, a secure alphanumeric application for textfiles, a secure software player application for software files, and soon. It is noted that secure player application 1810 can be configured tointeract with nearly any media type.

In one embodiment, secure player application 1810 can be a custom mediadevice 310 which can be an emulation of a custom media device driver(e.g., 307) as described herein with reference to FIGS. 3, 4, and FIGS.5A-5D. In another embodiment, secure player application 1810 can be anapproved player application as described herein with reference to FIG.3.

FIG. 19 is an exemplary system 1900 for controlling media sharing amongmultiple computer systems communicatively coupled in a network inaccordance with one embodiment of the present invention. System 1900includes client node 1705, a source node 1715, and an administrativenode 1770. Nodes 1705, 1715 and 1770 are implemented in andcommunicatively coupled to a network 1700 in one embodiment of thepresent invention. In one embodiment, network 1700 is a decentralizeddistributed network, (e.g., network 800 of FIG. 8).

In an embodiment, source node 1715 and client node 1705 have logged onto network 1700, as described herein with reference to FIG. 4, and steps702-716 of FIG. 7A. Client node 1705 requests an instance of media fromnetwork 1700, (e.g., 4321), shown as communication 1910. Network 1700transfers the request to administrative node 1770 which determines thelocation of an instance of media 4321. Administrative node 1770 respondsto client node 1705 with the location of instance of media 4321, shownas communication 1920.

In this example, administrative node 1770 is cognizant that source node1715 has an instance of media 4321 disposed therein. In the presentembodiment, instance of media content 4321 is stored in a protectedmedia container file by memory coupled to source node 1715.Additionally, instance of media 4321 is encrypted local to source node1715, shown as dotted line 1716 encompassing media 4321.

Within FIG. 19, source node 1715 sends a request to administrative node1770 for an intermediate encryption key to encrypt instance of media4321 for transfer to client node 1705, shown as communication 1930.Administrative node 1770 transmits an intermediate encryption key, (e.g.key 1775), to source node 1715. Upon receipt of intermediate encryptionkey 1775 by source node 1715, a client communication application 1820operable on source node 1715 decrypts media 4321 from its encryptionlocal thereto, (e.g., encryption 1716), and encrypts media 4321 into anintermediate encryption, as indicated by dotted line 1775 encompassingmedia 4321.

Still referring to FIG. 19, once client communication application 1820on source node 1715 encrypts media 4321 into intermediate encryption1775, client communication application 1820 transmits media 4321 inintermediate encryption 1775 to client node 1705, shown as communication1950. Upon client node 1705 receiving media 4321 in intermediateencryption 1775, client node 1705 sends a request to administrative node1770 for an intermediate decryption key (e.g., key 1776), shown ascommunication 1960. Intermediate decryption key 1776 enables a clientcommunication application 1820 operable on client node 1705 to decryptmedia 4321 from its intermediate encryption 1775. It is noted that untilintermediate encryption 1775 is decrypted, secure player 1810 operableon client node 1705 is unable to present media 4321 to system 1705. Itis further noted that if another computer system in network 1700 hasintercepted media 4321 during transfer, the intermediate encryption 1775prevents use of media 4321 by the intercepting computer system.

Continuing, administrative node 1770 responds to client node 1705request for an intermediate decryption key and transmits key 1776 toclient node 1705, shown as communication 1970. Once key 1776 is receivedby client node 1705, a client communication application 1820 operable onsystem 1705 decrypts media 4321 out of intermediate encryption 1775 andencrypts media 4321 into an encryption local to client computer system,(e.g., encryption 1706 encompassing media 4321).

When media 4321 has been successfully received by and encrypted into anencryption local to client node 1705, (e.g., media 4321 with encryption1706), client node 1705 transmits an acknowledge indicator indicatingsuccessful receipt of media 4321, shown as communication 1980.Accordingly, upon receipt of an acknowledge indictor, administrativenode 1770 generates a transaction applicable to client node 1705 andwhich is associated with media 4321.

Advantageously, embodiments of the present invention provide componentsthat enable controlled media sharing in a decentralized distributednetwork (a p2p network), e.g., network 800 of FIG. 8 and/or network 1700of FIG. 17. Further advantageous is that embodiments of the presentinvention can also track the sharing, generate royalties applicable to areceiving computer system and associated with a particular instance ofmedia. Also advantageous is that embodiments of the present inventionallow for outside instances of media to enter the network and providecompliance with copyright restrictions and licensing agreementsassociated with the instance of media.

It is noted that one or more embodiments in accordance with the presentinvention described herein can be utilized in combination with adelivery system similar to delivery system 800 of FIG. 8. For example,any network of one or more of the embodiments in accordance with thepresent invention can be substituted with a delivery system similar todelivery system 800. Alternatively, a delivery system similar todelivery 800 may be implemented to include any combination of sourcenodes (e.g., 1715), client nodes (e.g., 1705), and/or administrativenodes (e.g., 1770) that operate in any manner similar to that describedherein, but are not limited to such.

Media Change Notification

FIG. 20 is a block diagram 2000 of an exemplary computing environmentshown in accordance with an embodiment of the present invention.Computing environment 2000 is similar to the communicative environmentas shown in FIG. 10. Computing environment 2000 includes computingsystem 100, media device 2020, and media storage device 999. Computingsystem 100 is described in detail herein including FIG. 1. Media device2020 may be any device which can access (e.g., read, write, etc) themedia stored on media storage device 999. In one embodiment, mediadevice 2020 is removably coupled with computing system 210. In anotherembodiment, media device 2020 is internal to (or fixedly coupled with)computing system 210. As stated herein, media storage device 999 can be,but is not limited to, a CD, a DVD, or other optical or magnetic storagedevice. Embodiments of media on the media storage device 999 may includeaudio, video, multimedia, graphics, information, data, softwareprograms, and other forms of media that may or may not containcopyrighted material and which may be disposed on a media storage device999.

In general, the system 2000 is a generic example shown for purposes ofproviding a generic environment in which a media change notification ona computing system may occur. In general, a media change notificationoccurs when new media is detected in a media device. The reasons fordetecting media in a media device are important for a plurality ofpurposes. One purpose is that the detection of media allows thecomputing system to install operational components from a media storagedevice 999 thereby allowing access to the rest of the data stored onmedia storage device 999. Another purpose, as described herein, is thatthe detection of media initiates the autorun (or autoplay) protocolcomponent 910 features (described in FIG. 9) including the initialinstallation of CCM 300. However, as described herein, one deleteriousissue with the autorun (or autoplay) protocol component 910 is that auser may defeat autorun (or autoplay) protocol component 910.

With reference now to FIG. 21, a data flow block diagram 2100 of anexemplary method for providing a media change notification on acomputing system is shown in accordance with an embodiment of thepresent invention. Data flow block diagram 2100 shows the newnon-defeatable media change notification (MCN) protocol 2105 operatingin conjunction with autorun (or autoplay) protocol component 910 toovercome the problems of the present autorun (or autoplay) protocolcomponent 910.

Referring now to step 2105 of FIG. 21 and to FIG. 20, in one embodiment,a non-defeatable media change notification protocol is initiated. In oneembodiment, the initiation may occur at computing system 100 start-up.In addition, during start-up, a list of media devices 2020 may begenerated for all media devices 2020 communicatively coupled withcomputing system 100. This list may then be accessed by thenon-defeatable media change notification protocol of step 2105 to ensurethat all media devices 2020 operating on computer system 100 are known.

In one embodiment, the media change notification protocol 2105 may be amodification to the existing autorun (or autoplay) protocol component910, or the media change notification protocol 2105 may be a secondcomponent or plurality of components operating in parallel with autorun(or autoplay) protocol component 910. In either case, the autorun (orautoplay) protocol component 910 may operate without any changes withrespect to media devices (e.g., media device 2020 of FIG. 20) while themedia change notification protocol generates the MCN 2150 whenever anymedia 999 is introduced to the media device 2020. Therefore, to the userthere is no apparent change in the operation of the computing system 100to include the autorun (or autoplay) protocol component 910. However, tothe system, a signal (e.g., MCN 2150) is being generated. Specifically,the non-defeatable MCN protocol 2105 issues a MCN (e.g., a signal) whennew media is detected in the media device. This signal is generatedregardless of input to the computing system regarding the operation ofthe autorun (or autoplay) protocol component 910.

Referring now to step 2110 of FIG. 21 and to FIG. 20, in one embodimentthe autorun (or autoplay) protocol component 910 checks to see if it isenabled for each media device 2020. In one embodiment, the autorun (orautoplay) protocol component 910 may access the same list of mediadevices 999 as that of the media change notification protocol. If theautorun (or autoplay) protocol component 910 is not enabled for anymedia devices 2020 coupled with the computing system 100 then theautorun (or autoplay) protocol component 910 will exit 2120 for thatdevice.

Referring now to step 2130 of FIG. 21 and to FIG. 20, in one embodiment,if the autorun (or autoplay) protocol component 910 is enabled for themedia device 2020, then the autorun (or autoplay) protocol component 910will check to see if the media device 2020 is on a list of devices forwhich the autorun (or autoplay) protocol component 910 is never enabled.If the media device 2020 is on the list, then the autorun (or autoplay)protocol component 910 will exit for that device.

Referring now to step 2140 of FIG. 21 and to FIG. 20, in one embodiment,if the media device 2020 is not on the list of devices for which autorun(or autoplay) protocol component 910 is never enabled, then the autorun(or autoplay) protocol component 910 will begin polling the media device2020 for media 999. Further details of the autorun (or autoplay)protocol component 910 including code and pseudo-code are discussed indetail herein.

Referring now to step 2150 of FIG. 21 and to FIG. 20, in one embodiment,if media 999 is detected (e.g., new media 999, that is, media operatingin a media device that has been to this point unrecognized) then a mediachange notification is output.

With reference now to FIG. 22, a flowchart 2200 of a process forproviding a media change notification on a computing system is shown inaccordance with one embodiment of the present invention. In general, theprocess described herein allows for media change notification on acomputing system that cannot be blocked by user input or othermodifications to the computing system. In one embodiment, the mediachange notification may be performed at the kernel level with kernellevel drivers outputting a media change notification when a media change(e.g., media is introduced) occurs.

In another embodiment, the media change notification may be performed atthe user level. That is, the media change notification may be a program(or application) or portion of a program (or application) similar infunction to that described in FIG. 21. For example, the media contentnotification may be performed by modifying an existing autorun (orautoplay) protocol component 910. In so doing, the media pollingcomponent (e.g., autorun (or autoplay) protocol component 910) may polleach media device 2020 communicatively coupled with the computing system100 for media regardless of any input to said media polling component(e.g., autorun (or autoplay) protocol component 910) by said computingsystem 100 or user thereon. In one embodiment, if the autorun (orautoplay) protocol component 910 is disabled for the media device havingthe new media, a media content notification will still be output by theautorun (or autoplay) protocol component 910, however, the autorun (orautoplay) protocol component 910 perform no other action. That is, otherthan the output of the notification, no further action by the autorun(or autoplay) protocol component 910 will take place.

In yet another embodiment, the media content notification may beperformed by a second component or components operating in parallel witha first component (e.g., an autorun (or autoplay) protocol component910). In so doing, the first component (e.g., autorun (or autoplay)protocol component 910) may be disabled from polling each media device2020 communicatively coupled with the computing system 100. However, thesecond component or components (e.g., media change notificationprotocol) will poll the media device 2020 for media regardless of anyinput by said computing system 100 or user acting thereon.

Referring now to step 2202 of FIG. 22 and to FIG. 20, in one embodimentmedia device of a computing system is polled for a media change, whereinthe polling of the media device cannot be blocked by the computingsystem. As stated herein, in one embodiment, the media change is anintroduction of media 999 to the media device 2020.

With reference now to step 2204 of FIG. 22 and to FIG. 20, in oneembodiment, a media change is detected on the media device. For example,media 999 has been introduced to media device 2020. This introduction ofnew media 999 may be detected at the user level or at the kernel leveldepending on the location of the media change notification protocol. Inone embodiment, the media change notification protocol may be at boththe user level and the kernel level.

Referring now to step 2206 of FIG. 22 and to FIG. 20, in one embodiment,a media change notification (MCN) is generated when the media change isdetected. The MCN may be a signal, pulse, application, or the like. TheMCN may be system wide or the MCN may be directed to a specific driver,application, component, or the like.

With reference now to step 2208 of FIG. 22 and FIG. 20, the media changenotification is output when the media change on the media device isdetected, furthermore, the media change notification cannot be blockedby the computing system. For example, a user may not disable the MCNprotocols and the computing system may not be manipulated to stop thegeneration or the output of the MCN. Therefore, when any media 999 isreceived by a media device 2020, components within the computing system100 will output a MCN which cannot be obstructed. Therefore, each timemedia 999 is inserted into a media device 2020 and is accessible bycomputing system 100 a signal (e.g., MCN) will also be present.

Automatic Execution

With reference now to FIG. 23, a flowchart of a method for automaticallyexecuting an operation after a media event is shown in accordance withone embodiment of the present invention. In general, the method forautomatically executing an operation is the second part of the overallmethod for establishing a non-defeatable autorun (or autoplay)environment within a computer system such as computing system 100 ofFIG. 1, and more specifically, in an environment such as the computingenvironments of FIGS. 10 and 14.

In one embodiment, as described in detail herein, media content isintroduced (e.g., a media event) to a computing system such as computingsystem 100. The media content may be introduced (or the media event mayoccur) from a storage device local to the computing system, or the mediacontent may be introduced from a network, such as a local area network(LAN) or the Internet, or the like. Additionally, the media content maybe audio, video, or a combination of audio and video. After the media isintroduced (e.g., a media event), a media change notification (MCN) isgenerated, as described herein. Flowchart 2300 commences as the MCN isreceived by a program on the computing system 100.

With reference now to step 2302 of FIG. 23, a media change notificationis received from a non-defeatable media detector such as the mediachange notification generator described herein when a media eventoccurs. As described in detail herein, the MCN may be a signal, pulse,application, or the like. The MCN may be system wide or the MCN may bedirected to a specific driver, application, component, or the like. Ingeneral, the MCN is received by an application, driver, component, orthe like (referred to herein as an application for purposes of brevityand clarity). In one embodiment, the application is operating orresiding in the background of computing system 100. Moreover, the MCNmay be received at the user level, at the kernel level, or at both theuser and the kernel level.

Referring now to step 2304 of FIG. 23, in one embodiment, a filecorresponding to the media event responsible for the MCN is accessed.For example, when the MCN is received, the application that received theMCN may look for a file with a given file name or at a given filelocation on the media event (or media). In another embodiment, theapplication may look for a flag in the content of the media. The flag inthe media may be a file name or location that may be used in conjunctionwith the introduced media. For example, the flag in the media may signala copyright indicator that may provide copyright information about themedia, or actions that may need to be taken due to copyright or otherrestrictions. In another embodiment, the application may send up a flaginforming a second application on computing system 100 of the insertionof media into the computing system 100.

In one embodiment, the media file operates in a manner similar to thatof conventional self-installing or self-running program. That is, theactivation of the file in the media by the application that received theMCN may activate instructions for installing or running other componentsimmediately upon media insertion. In another embodiment, the file may beempty, indicating that no action is to be performed.

In general, the program file may be in the form of an executableprogram, a series of system configuration definitions, or a series ofdirectives to find/download/install the latest version of the protectivesoftware via the web. Furthermore, the distribution media may contain alibrary or libraries of files, songs, movies, or other media to protectand may further contain the location information to find the latestversion of these libraries. These libraries may be specific toindividual copyright holders or hold some more general information thatmay indicate the rights of a particular class of content (e.g., homeuser created, public domain, never copy, copy once, copy X times, etc.).

With reference now to step 2306 of FIG. 23, in one embodiment, the filecorresponding to the media event are authenticated. That is, afterfinding the file on the media, the application activated by the MCN willauthenticate the file and information contained therein to ensureauthenticity. For example, the file may contain instructions,applications, instructions for accessing an application on the computingsystem 100, accessing applications or instructions on both the media andthe computing system 100, directions to access the Internet (e.g., a URLor the like), accessing a dongle (e.g., a PCMCIA card, a parallel port,USB port, biometric, or the like), etc. Thus, the file or instructionsthereon may direct the computing system 100 to a plurality of locationsfor accessing, installing, and/or running an application or applicationsautomatically (e.g., without a users input or guidance). Therefore, itis necessary to authenticate the file and any information containedthereon to ensure that a virus, Trojan, or other illegal application isnot being delivered, or initialized on computing system 100.

For example, if copyright protocols are being accessed, the applicationreceiving the MCN may read and establish the copyright protocol file, orportions thereof, to authenticate the inserted media (e.g., authorizeone copy, no copies, unlimited copies, or the like). Additionally, thesource of the content of the file and the media may be authenticated.For example, the software may be “signed,” encrypted or otherwiseprotected (e.g., digital certificates, passwords, trusted locations,etc. may be checked to ensure the information being accessed islegitimate) to prevent a malicious software installation includingvirus, Trojan, false library files, or the like.

This technology could also look for the existence of copyright bits setin a table of contents, a copyright flag within the media, the existenceof an encryption method, or a copy protect “file.” Additionally, thesoftware that resides on the computer system 100 may also be signed toprevent removal or modification (e.g., signed drivers, encryption,etc.). For example, multilayer or dual sided disks may be used to storethe software protection and libraries therefore allowing for multipleoperating system software, multiple versions of the same operatingsystem, and/or large library files. In one embodiment, the softwareoperating on computing system 100 may be installed via one of theplurality of methods described in detail herein. For example, operatingsystem and/or application software upgrades, via bundling with playerapplications, online installs, bundled with protected media content,written into the operating system, or the like.

Referring now to step 2308 of FIG. 23, in one embodiment, theinstructions contained on the file are executed. That is, once theauthorization process is complete, the operations specified in the fileare executed. For example, the instructions may include the download ofa driver or drivers, or the instructions may pertain to copyright issuessuch as an authorization of a single play, no copy, one copy, etc.Furthermore, the accessing, authenticating, and executing of contentcontained on the file cannot be defeated, turned off, blocked,overridden, or the like by a user.

Once the steps 2302 through 2308 have been performed, the computingsystem 100 then returns to operation as normal. That is, the traditionalautorun (or autoplay) will or will not occur. For example, if the userhas not turned off the autorun feature, any programs or files that arenormally run by autorun will occur. However, if the user has turned offthe autorun (or autoplay) feature, no programs or files willautomatically open. Therefore, unlike traditional user controlledinstallation mechanisms, the steps 2302 through 2308 cannot be turnedoff or modified by the user.

Therefore, one embodiment, allows the copyright holder or contentmanufacturer to provide whatever form of protection they desire for eachindividual product. Additionally, business rules could also beestablished regarding the type of protection and the number of copiesthat may be made of the copyrighted material.

Thus, an advantage of the non-defeatable autorun package is that it doesnot impose any particular DRM strategy on either the producers orconsumers of copyrighted material. It also allows the OS supplier tocooperate with the DRM efforts of the entertainment industry withoutimposing DRM controls of its own. For example, the method and systemdescribed herein allows the media producers to supply and imposewhatever protection mechanism, or lack thereof, that they wish. It alsoallows different products to have different levels of protection,perhaps based on the value of the contents or the pricing of theproduct. The important point is that the non-defeatable autorunmechanism ensures DRM capabilities but gives individual movie studiosand record companies control over the DRM controls of their products.Additionally, the consumer is also given the choice to accept or declinethe DRM components, since nothing is installed on the user's computeruntil the media is actually inserted. Given that different products canhave different levels and types of DRM protection, the user can choosethose products that offer the most desirable content with the leastobtrusive protection.

Interaction Control

With reference now to FIG. 24, a data flow block diagram forautomatically detecting media and implementing interaction controlthereon, is shown in accordance with one embodiment of the presentinvention.

With reference now to step 2405 of FIG. 24, in one embodiment a mediachange notification (MCN) is received after a media event. As describedherein, the media event may be a media content introduction from astorage device local to the computing system, or the media content maybe introduced from a network, such as a local area network (LAN) or theInternet, or the like. Additionally, the media content may be audio,video, or a combination of audio and video. After the media isintroduced (e.g., a media event), a media change notification (MCN) isgenerated, as described herein.

The media change notification is received from a non-defeatable mediadetector such as the media change notification generator describedherein when a media event occurs. As described in detail herein, the MCNmay be a signal, pulse, application, or the like. The MCN may be systemwide or the MCN may be directed to a specific driver, application,component, or the like. In general, the MCN is received by anapplication, driver, component, or the like (referred to herein as anapplication for purposes of brevity and clarity). In one embodiment, theapplication is operating or residing in the background of computingsystem 100. Moreover, the MCN may be received at the user level, at thekernel level, or at both the user and the kernel level.

Referring now to step 2410 of FIG. 24, in one embodiment, an operationis executed based on the reception of the MCN. For example, a mediachange notification is received from a non-defeatable media detectorsuch as the media change notification generator described herein when amedia event occurs. As described in detail herein, the MCN may be asignal, pulse, application, or the like. The MCN may be system wide orthe MCN may be directed to a specific driver, application, component, orthe like. In general, the MCN is received by an application, driver,component, or the like (referred to herein as an application forpurposes of brevity and clarity). In one embodiment, the application isoperating or residing in the background of computing system 100.Moreover, the MCN may be received at the user level, at the kernellevel, or at both the user and the kernel level.

With reference now to step 2415 of FIG. 24, in one embodiment, a filecorresponding to the media event is accessed. For example, when the MCNis received, the application that received the MCN may look for a filewith a given file name or at a given file location on the media event(or media). In another embodiment, the application may look for a flagin the content of the media. The flag in the media may be a file name orlocation that may be used in conjunction with the introduced media. Forexample, the flag in the media may signal a copyright indicator that mayprovide copyright information about the media, or actions that may needto be taken due to copyright or other restrictions. In anotherembodiment, the application may send up a flag informing a secondapplication on computing system 100 of the insertion of media into thecomputing system 100.

Referring now to step 2420 of FIG. 24, in one embodiment, a filecorresponding to the media event is checked. As described herein, thefile corresponding to the media event may contain instructions,applications, instructions for accessing an application on the computingsystem 100, accessing applications or instructions on both the media andthe computing system 100, directions to access the Internet (e.g., a URLor the like), accessing a dongle (e.g., a PCMCIA card, a parallel port,USB port, biometric, or the like), etc.

With reference now to step 2425 of FIG. 24, in one embodiment, the fileis checked for data. If the file does not contain data, then step 2430the action is ended and the system awaits the next MCN. However, if thefile does contain data then step 2435, the data in the file isauthenticated. As described herein, the file or instructions thereon maydirect the computing system 100 to a plurality of locations foraccessing, installing, and/or running an application or applicationsautomatically (e.g., without a users input or guidance). Therefore, itis necessary to authenticate the file and any information containedthereon to ensure that a virus, Trojan, or other illegal application isnot being delivered, or initialized on computing system 100.

For example, if copyright protocols are being accessed, the applicationreceiving the MCN may read and establish the copyright protocol file, orportions thereof, to authenticate the inserted media (e.g., authorizeone copy, no copies, unlimited copies, or the like). Additionally, thesource of the content of the file and the media may be authenticated.For example, the software may be “signed,” encrypted or otherwiseprotected (e.g., digital certificates, passwords, trusted locations,etc. may be checked to ensure the information being accessed islegitimate) to prevent a malicious software installation includingvirus, Trojan, false library files, or the like.

With reference now to step 2445 of FIG. 24, in one embodiment, the datain the file is analyzed to establish whether it is information or aprogram. If the data in the file is information and not a program, thenstep 2450, a media control program (e.g., X1 described in detail herein)is activated. Once the media control program is activated, as describedherein, the interaction with the media is controlled based on the mediarules in the data file, or on media rules stored in the media controlprogram based on the data received from the data in the file.

Referring now to step 2450 of FIG. 24, in one embodiment, if the data inthe file is a program, the program is automatically downloaded and/orinstalled. In another embodiment, the data in the file may be a link toa secondary site that contains the program to be downloaded prior toproviding a user access to the rest of the media content on the mediaevent.

With reference now to step 2455 of FIG. 24, in one embodiment,interaction with the media is controlled based on the media rules in thedata file or the rules linked by the data file on the media, or by datain the media file directed to rules stored outside the media. That is,once the authorization process is complete, the operations specified inthe file are executed. For example, the instructions may include thedownload of a driver or drivers, or the instructions may pertain tocopyright issues such as an authorization of a single play, no copy, onecopy, etc. Furthermore, the accessing, authenticating, and executing ofcontent contained on the file cannot be defeated, turned off, blocked,overridden, or the like by a user.

Once the steps 2405 through 2460 have been performed, the computingsystem 100 then returns to operation as normal. That is, the traditionalautorun (or autoplay) will or will not occur. For example, if theautorun feature is active, any programs, files or functions that arenormally run/performed by autorun will occur. However, if the user hasdisabled the autorun (or autoplay) feature, no programs or files willautomatically be opened by the traditional autorun. However, asdescribed herein, unlike traditional user controlled installationmechanisms, the steps 2405 through 2460 will not be turned off ormodified by the user.

Therefore, one embodiment, allows the copyright holder or contentmanufacturer to provide whatever form of protection they desire for eachindividual product. Additionally, business rules could also beestablished regarding the type of protection and the number of copiesthat may be made of the copyrighted material.

Thus, an advantage of the non-defeatable autorun package is that it doesnot impose any particular DRM strategy on either the producers orconsumers of copyrighted material. It also allows the OS supplier tocooperate with the DRM efforts of the entertainment industry withoutimposing DRM controls of its own. For example, the method and systemdescribed herein allows the media producers to supply and imposewhatever protection mechanism, or lack thereof, that they wish. It alsoallows different products to have different levels of protection,perhaps based on the value of the contents or the pricing of theproduct. The important point is that the non-defeatable autorunmechanism ensures DRM capabilities but gives individual movie studiosand record companies control over the DRM controls of their products.Additionally, the consumer is also given the choice to accept or declinethe DRM components, since nothing is installed on the user's computeruntil the media is actually inserted. Given that different products canhave different levels and types of DRM protection, the user can choosethose products that offer the most desirable content with the leastobtrusive protection.

With reference now to FIG. 25, a flowchart of a method for automaticallydetecting media and implementing interaction control thereon is shown inaccordance with one embodiment of the present invention.

Referring now to step 2502 of FIG. 25, in one embodiment, an MCN isreceived from a non-defeatable media detector. In general operation, thenon-defeatable media detector initially poles a media device of acomputing system for a media change wherein the polling of the mediadevice cannot be blocked by the computing system. When thenon-defeatable media detector detects a media change on the media devicea media change notification is generated. Moreover, the media changenotification is output to the computing system when the media change isdetected.

With reference now to step 2504 of FIG. 25, in one embodiment, anoperation is executed automatically after receiving the MCN of the mediaevent. In general, the execution of the operation automatically afterthe media event includes receiving the MCN from the non-defeatable mediadetector. In addition, a file is accessed corresponding to the mediaevent responsible for the MCN. The file corresponding to the media eventis authenticated, and any instructions contained on the file areexecuted. In one embodiment, the accessing, authenticating, andexecuting of the content contained on the file cannot be defeated,stopped, interrupted, or overridden by a user.

As described in detail herein, the content in the file may containinstructions for installing or running other components, e.g., the X1technology or another copyright compliance mechanism. The instructionsmay include an executable program, a system configuration definition, aseries of system configuration definitions, a directive to find,download, and/or install protection software, or a series of directivesto find, download, and/or install protection software. In oneembodiment, the instruction is a copyright bits set located in a tableof contents, a copyright flag within the media, a copy protect file, oran encryption method.

With reference now to step 2506 of FIG. 25, in one embodiment, acontroller for controlling interaction of deliverable electronic mediafrom a media file corresponding to the media event is initiated via theoperation, wherein the receiving, executing, and controlling areautomatically implemented and cannot be defeated by a user.

In one embodiment, controlling interaction of deliverable electronicmedia includes detecting a media player application operable with acomputer system for enabling the computer system to present contents ofa media file. In addition, within the media player application afunction that enables non-compliance with a usage restriction applicableto the media file is generated. Moreover, the output of the media fileis controlled by a compliance mechanism coupled to the computer systemfor enabling compliance with the usage restriction applicable to themedia file.

In general, the controlling output of the media file includes divertinga data pathway of the media player application to a controlled datapathway controlled by the compliance mechanism. In addition, if nocontrolling mechanism is present on the computing system, the compliancemechanism can be installed onto the computing system and configured todetect and disable any unauthorized access, copying, uploading,downloading, or the like. In one embodiment, the compliance mechanisminstalls its own custom media player application on the computing systemconfigured to operate when the user preferred media player applicationdoes not comply with usage restrictions detailed in the media file. Thecompliance mechanism (e.g., X1 or the like) may monitor the media file,the computing system, and any periphery devices during the presentationof the media content for compliance with the usage restrictions.

Thus, embodiments of the present invention provide a method forautomatically detecting media and implementing interaction controlthereon. Further, embodiments of the present invention provide a methodfor automatically detecting media and implementing interaction controlthereon that cannot be turned off, blocked, or disabled by a user.Embodiments of the present invention also provide a method forautomatically detecting media and implementing interaction controlthereon which is compatible with industry standards.

The foregoing disclosure regarding specific embodiments of the presentinvention has been presented for purposes of illustration anddescription. They are not intended to be exhaustive or to limit theinvention to the precise forms disclosed, and many modifications andvariations are possible in light of above teaching. The embodiments werechosen and described in order to best explain the principles of theinvention and its practical application, to thereby enable othersskilled in the art to best utilize the invention and various embodimentswith various modifications as are suited to the particular usecontemplated. It is intended that the scope of the invention be definedby the Claims appended hereto and their equivalents.

What is claimed is:
 1. A method for automatically detecting media andimplementing interaction control thereon comprising: receiving a mediachange notification (MCN) from a non-defeatable media detector;executing an operation automatically after receiving said MCN of a mediaevent; and initiating a controller for controlling interaction ofdeliverable electronic media from a media file corresponding to saidmedia event via said operation, wherein said receiving, executing, andcontrolling are automatically implemented and cannot be defeated by auser.
 2. The method of claim 1 wherein said non-defeatable mediadetector comprises: polling a media device of a computing system for amedia change wherein said polling of said media device cannot be blockedby said computing system; detecting said media change on said mediadevice; generating said media change notification when said media changeis detected; and outputting said media change notification when saidmedia change on said media device is detected.
 3. The method of claim 1wherein said executing an operation automatically after said media eventfurther comprises: receiving said media change notification (MCN) fromsaid non-defeatable media detector; accessing a file corresponding tosaid media event responsible for the MCN; authenticating said filecorresponding to said media event; and executing an instructioncontained on said file, wherein said accessing, authenticating, andexecuting of content contained on said file cannot be defeated by auser.
 4. The method of claim 1 wherein said controlling interaction ofdeliverable electronic media comprising: detecting a media playerapplication operable with a computer system, said media playerapplication for enabling said computer system to present contents ofsaid media file; governing within said media player application afunction that enables non-compliance with a usage restriction applicableto said media file; and controlling the output of said media file, saidcontrolling by a compliance mechanism coupled to said computer system,said compliance mechanism for enabling compliance with said usagerestriction applicable to said media file.
 5. The method of claim 2wherein said media change notification cannot be blocked by saidcomputing system.
 6. The method of claim 3 wherein said content in saidfile comprises an instruction for installing or running othercomponents.
 7. The method of claim 3 wherein said instruction isselected from the group of instructions including: an executableprogram, a system configuration definition, a series of systemconfiguration definitions, a directive to find, download, and/or installprotection software, or a series of directives to find, download, and/orinstall protection software.
 8. The method of claim 3 wherein saidinstruction is a copyright bits set located in a table of contents, acopyright flag within the media, a copy protect file, or an encryptionmethod.
 9. The method of claim 4 wherein said controlling output of saidmedia file comprises diverting a data pathway of said media playerapplication to a controlled data pathway, and wherein said compliancemechanism controls said controlled data pathway.
 10. The method of claim4 further comprising installing said compliance mechanism onto saidcomputer system, said compliance mechanism configured to perform saiddetecting and said disabling.
 11. The method of claim 4 furthercomprising installing a custom media player application on said computersystem and configured to be operable when said media player applicationdoes not comply with said usage restriction.
 12. The method of claim 4further comprising monitoring said media file during presentation ofsaid contents for compliance with said usage restrictions, saidmonitoring performed by said compliance mechanism.
 13. A computerreadable medium for storing computer implementable instructions, saidinstructions for causing a client system to perform a method forautomatically detecting media and implementing interaction controlthereon comprising: receiving a media change notification (MCN) from anon-defeatable media detector; executing an operation automaticallyafter receiving said MCN of a media event; and initiating a controllerfor controlling interaction of deliverable electronic media from a mediafile corresponding to said media event via said operation, wherein saidreceiving, executing, and controlling are automatically implemented andcannot be defeated by a user.
 14. The computer readable medium of claim13 wherein said non-defeatable media detector comprises: polling a mediadevice of a computing system for a media change wherein said polling ofsaid media device cannot be blocked by said computing system; detectingsaid media change on said media device; generating said media changenotification when said media change is detected; and outputting saidmedia change notification when said media change on said media device isdetected.
 15. The computer readable medium of claim 13 wherein saidexecuting an operation automatically after said media event furthercomprises: receiving said media change notification (MCN) from saidnon-defeatable media detector; accessing a file corresponding to saidmedia event responsible for the MCN; authenticating said filecorresponding to said media event; and executing an instructioncontained on said file, wherein said accessing, authenticating, andexecuting of content contained on said file cannot be defeated by auser.
 16. The computer readable medium of claim 13 wherein saidcontrolling interaction of deliverable electronic media comprising:detecting a media player application operable with a computer system,said media player application for enabling said computer system topresent contents of said media file; governing within said media playerapplication a function that enables non-compliance with a usagerestriction applicable to said media file; and controlling the output ofsaid media file, said controlling by a compliance mechanism coupled tosaid computer system, said compliance mechanism for enabling compliancewith said usage restriction applicable to said media file.
 17. Thecomputer readable medium of claim 14 wherein said media changenotification cannot be blocked by said computing system.
 18. Thecomputer readable medium of claim 15 wherein said content in said filecomprises an instruction for installing or running other components. 19.The computer readable medium of claim 15 wherein said instruction isselected from the group of instructions including: an executableprogram, a system configuration definition, a series of systemconfiguration definitions, a directive to find, download, and/or installprotection software, or a series of directives to find, download, and/orinstall protection software.
 20. The computer readable medium of claim15 wherein said instruction is a copyright bits set located in a tableof contents, a copyright flag within the media, a copy protect file, oran encryption method.
 21. The computer readable medium of claim 16wherein said controlling output of said media file comprises diverting adata pathway of said media player application to a controlled datapathway, and wherein said compliance mechanism controls said controlleddata pathway.
 22. The computer readable medium of claim 16 furthercomprising installing said compliance mechanism onto said computersystem, said compliance mechanism configured to perform said detectingand said disabling.
 23. The computer readable medium of claim 16 furthercomprising installing a custom media player application on said computersystem and configured to be operable when said media player applicationdoes not comply with said usage restriction.
 24. The computer readablemedium of claim 16 further comprising monitoring said media file duringpresentation of said contents for compliance with said usagerestrictions, said monitoring performed by said compliance mechanism.25. A system for method for automatically detecting media andimplementing interaction control thereon comprising: a means forreceiving a media change notification (MCN) from a non-defeatable mediadetector; a means for executing an operation automatically afterreceiving said MCN of a media event; and a means for initiating acontroller for controlling interaction of deliverable electronic mediafrom a media file corresponding to said media event via said operation,wherein said receiving, executing, and controlling are automaticallyimplemented and cannot be defeated by a user.
 26. The system as recitedin claim 25 wherein said non-defeatable media detector comprises: ameans for polling a media device of a computing system for a mediachange wherein said polling of said media device cannot be blocked bysaid computing system; a means for detecting said media change on saidmedia device; a means for generating said media change notification whensaid media change is detected; and a means for outputting said mediachange notification when said media change on said media device isdetected.
 27. The system as recited in claim 25 wherein said means forexecuting an operation automatically after said media event furthercomprises: a means for receiving said media change notification (MCN)from said non-defeatable media detector; a means for accessing a filecorresponding to said media event responsible for the MCN; a means forauthenticating said file corresponding to said media event; and a meansfor executing an instruction contained on said file, wherein saidaccessing, authenticating, and executing of content contained on saidfile cannot be defeated by a user.
 28. The system as recited in claim 26wherein said means for controlling interaction of deliverable electronicmedia comprising: a means for detecting a media player applicationoperable with a computer system, said media player application forenabling said computer system to present contents of said media file; ameans for governing within said media player application a function thatenables non-compliance with a usage restriction applicable to said mediafile; and a means for controlling the output of said media file, saidcontrolling by a compliance mechanism coupled to said computer system,said compliance mechanism for enabling compliance with said usagerestriction applicable to said media file.
 29. The system as recited inclaim 26 wherein said means for media change notification cannot beblocked by said computing system.
 30. The system as recited in claim 26wherein said content in said file comprises a means for installing orrunning other components.
 31. The system as recited in claim 27 whereinsaid instruction is selected from the group of instructions including:an executable program, a system configuration definition, a series ofsystem configuration definitions, a directive to find, download, and/orinstall protection software, or a series of directives to find,download, and/or install protection software.
 32. The system as recitedin claim 27 wherein said instruction is a copyright bits set located ina table of contents, a copyright flag within the media, a copy protectfile, or an encryption method.
 33. The system as recited in claim 28wherein said means for controlling output of said media file comprisesdiverting a data pathway of said media player application to acontrolled data pathway.
 34. The system as recited in claim 28 furthercomprising a means for installing said compliance mechanism onto saidcomputer system, said compliance mechanism a means to perform saiddetecting and said disabling.
 35. The system as recited in claim 28further comprising a means for installing a custom media playerapplication on said computer system and configured to be operable whensaid media player application does not comply with said usagerestriction.
 36. The system as recited in claim 28 further comprising ameans for monitoring said media file during presentation of saidcontents for compliance with said usage restrictions.